Enable Security Compliance on a node

Security Compliance adds threat detection, integrity monitoring, and security analysis for a node, billed per month per node. It is available for nodes in Delhi, other than FortiGate nodes, nodes attached to a VPC with Custom CIDR, and nodes on the older Xen hypervisor. Turning it on in the portal is the first step. You then connect the monitoring agent from inside the node, over SSH, or over RDP for a Windows node.

Turn on Security Compliance

1. Open the node’s actions. In the node list, open the node’s Actions menu. On the node’s own page, open Actions, then Security.
2. Click Enable Security Compliance. A dialog opens showing the monthly, per-node charge.
3. Turn on I want to start Security Compliance for this Node.
4. The charge starts when you click Enable, before the agent connects. Click Enable.

Enable registers the node with E2E’s compliance server. Setup commands appear right after you click it; copy them to run inside the node.

Connect the agent inside the node

Sign in to the node over SSH, or over RDP for a Windows node. Run the commands from the tab that matches the node’s package manager, or from the CMD tab on Windows. They carry this node’s own registration key, so they work only on this node. For the Linux commands, and how to check that the agent is running and connected, see Get started with Security Compliance.

Check that the agent connected

Open the node’s page. Until the agent connects, a warning there tells you to sign in to the node and run the commands. Its commands link shows them again.

Once the agent connects, the warning is replaced by Security Compliance is active on your Node., with a link to the Security Compliance page. That page counts your agents as active, disconnected, or never connected, so an agent that stops reporting later is counted there. To find your way around it, see Read the Security Compliance dashboard.

If the warning stays, see Troubleshooting Security Compliance and Troubleshooting node security and access.

Turn off Security Compliance

Open Actions, then Security, and click Disable Security Compliance. To confirm, click Disable. The Security Compliance charge ends, and the month you turn it off in is charged in full.

For protection against attacks from the internet as well, see Activate BitNinja on a node.