McAfee EPOCDE-AA-BA Product Guide - Page 64

7 Configuring advanced server settings Managing security keys 3 Edit the Sensors per Subnet field to set the maximum number of sensors active in each subnet, or select All sensors active. 4 Add a list of Sensor Scanning MAC addresses and OUIs that the sensors should not actively probe, regardless of the configured policy. 5 Edit the Active Period time field to set the maximum amount of time that passes before the server tells a sensor to sleep, to allow a new sensor to become active. The Active Period setting does not set the communication times for the active and inactive sensors. Communication time is configured using communication policy settings for Rogue System Detection. 6 Click Save. Managing security keys Security keys are used to verify and authenticate communications and content within your ePolicy Orchestrator managed environment. Contents Security keys and how they work Master repository key pair Agent-server secure communication (ASSC) keys Backing up and restoring keys Security keys and how they work The ePolicy Orchestrator server relies on three security key pairs. The three security pairs are used to: • Authenticate agent-server communication. • Verify the contents of local repositories. • Verify the contents of remote repositories. Each pair's secret key signs messages or packages at their source, while the pair's public key verifies the messages or packages at their target. Agent-server secure communication (ASSC) keys • The first time the agent communicates with the server, it sends its public key to the server. • From then on, the server uses the agent public key to verify messages signed with the agent's secret key. • The server uses its own secret key to sign its message to the agent. • The agent uses the server's public key to verify the agent's message. • You can have multiple secure communication key pairs, but only one can be designated as the master key. 64 McAfee® ePolicy Orchestrator® 4.6.0 Software Product Guide