Skip to content

Security Compliance

View as Markdown

Security Compliance watches the security of your E2E nodes and shows what it finds on one dashboard in MyAccount. It runs on Wazuh, an open-source security tool. You install the Wazuh agent inside a node, and the agent sends the following to E2E’s compliance server:

  • Security events, such as failed and successful logins.
  • Changes to files.
  • Known flaws in the packages installed on the node, listed as vulnerabilities.
  • Alerts mapped to the MITRE ATT&CK knowledge base and to the PCI DSS and HIPAA standards.

Security Compliance is available for nodes in Delhi, and you turn it on one node at a time from the node’s actions. Each node you turn it on for counts as one agent on the dashboard, and Enable Security Compliance on a node has the steps.

In the MyAccount side menu, click Security Compliance. The Security Compliance page opens and counts your agents as active, disconnected, or never connected. Once at least one agent is active, it links to the six views: Security events, Integrity monitoring, Vulnerabilities, MITRE ATT&CK, PCI DSS, and HIPAA. Searching MyAccount for Node security compliance opens the same page.

Once a node’s agent has connected, the node’s page reads Security Compliance is active on your Node. and links to the dashboard.

E2E bills each node with Security Compliance on for a monthly Compliance License, from the moment you turn it on. For how the charge starts and ends, see When does the charge start and stop?.

To connect your first node and see its alerts, follow Get started with Security Compliance. For help getting an agent active, see Troubleshooting Security Compliance. The Security Compliance FAQ has short answers about nodes, billing, and the data the dashboard keeps.