Access to eero logs for to investigate security threats
In case a security threat is detected and blocked on a device, eero provides limited information about the event, e.g. threat category and number of instances.
eero should allow user to access device logs to allow the investigation about the occurred issue and conduct root cause analysis.
I’m currently researching the 802.11 standard to see how much logging and how much access to those logs is mandatory for these devices to be considered compliant. Based on some responses to other questions in the subreddit, it seems that the engineers are very motivated to keep the system standards-compliant.
Not showing us the details of the threat blocked (source, destination, even the IOC) is a big problem. If I have malware beaconing to a c2 I want to investigate the device in my house….but count and no details just leaves me hanging.
- 1 yr agoLast active