Detecting Rogue Systems
Configuring server settings for Rogue System Detection
Configuring server settings for Rogue System
Detection
Use these tasks to configure server settings for Rogue System Detection. These settings
determine how information about subnets and detected systems is displayed in the Detected
Systems homepage. Server settings allow you to customize Rogue System Detection to meet
the specific needs of your organization.
Tasks
Editing compliance settings
Editing matching settings
Editing sensor settings
Editing compliance settings
Use this task to edit the Rogue System Compliance settings. These settings are user-configured
and have two important functions:
• They specify the time-frames that determine the state of detected systems (Managed,
Rogue, Exception, Inactive).
• They control the visual feedback of the Rogue System Detection status monitors on the
Detected Systems homepage.
Task
For option definitions, click ? on the page displaying the options.
1
Go to Configuration | Server Settings, then in the Settings Categories list click
Rogue System Compliance.
2
In the details pane click Edit.
3
Edit the number of days to categorize Detected Systems as Managed or Inactive.
NOTE:
The number of days in Rogue | Has Agent in ePO Database, but is older
than__ days is controlled by the number of days set in the Managed field.
4
Edit the percentage levels for these options, so that the color codes represent your
requirements:
• Covered Subnets — required coverage.
• System Compliance — required compliance status.
• Sensor Health — ratio of active to missing sensors.
5
Click Save.
Editing matching settings
Use this task to edit the matching settings for Rogue System Detection. Matching settings are
user-configured and have these important functions:
• They define the properties that determine how newly detected interfaces are matched with
existing systems.
• They specify static IP ranges for matching.
McAfee ePolicy Orchestrator 4.0.2 Product Guide
199