appears next to the control
statement if the control has been deprecated. A workflow is provided in
the Policy Editor for replacing deprecated controls.When detailed results are grouped by hosts, then each host in the report is listed with the host's IP address, DNS name, NetBIOS name and operating system. The OS CPE name appears only when the OS CPE feature is enabled for the subscription, and an authenticated scan was run on this host after enabling this feature.
When a host summary is included in the report, the following information appears for each host.
Controls. The number of controls in the policy that were evaluated on this host (sum of passed and failed).
Passed. The number of controls in the policy that passed on this host.
Failed. The number of controls in the policy that failed on this host.
Approved Exceptions. The number of approved exceptions on this host.
Pending Exceptions. The number of pending exceptions on the host.
Last Scan Date. The date and time the host was last scanned for compliance. If the host was found alive during the most recent compliance scan, the scan's date becomes the last scan date, regardless of whether authentication to the host was successful.
A list of controls evaluated on the host appears, sorted by technology. The controls are listed in the same order and in the same sections as the policy that you're reporting on.
Instance: Each control is listed with the section number in the policy, the control ID, and the control statement. If the control applies to a technology version, like an Oracle version, the instance information detected by the scanning engine appears in this format: (Oracle technology version:SID:port). For example: (Oracle10:ora102030p:1521).
appears next to the control
statement if the control has been deprecated. A workflow is provided in
the Policy Editor for replacing deprecated controls.
Status: Each control has a Passed or Failed status. The status is determined when the expected value for a control is compared to the actual value for the control. The expected value is defined in the compliance policy. The actual value is returned during the last compliance scan on the host.
Passed. A status of Passed indicates that the expected value and the actual value match.
Failed. A status of Failed indicates that the expected value and the actual value do not match.
PassedE. A status of PassedE indicates that the host is exempt from the control. This means that an exception was requested and accepted for the control on the host.
You can view control information for any control in the list by selecting the control ID number. When you do so, the Technical Control Information page appears with general control information, a list of technologies that the control applies to, a list of frameworks, standards and regulations that the control maps to, and user-provided comments for the control. This same information may be included in the glossary section of the report. Having this information in the glossary section of the report is especially useful if you want to print the report or distribute the report to users outside of the application. See Control Glossary for more information.
The following additional information may be included for each control, depending on your policy report template settings. Click the arrow next to any control to expand control details. (To expand details for all controls in the report, select Expand All from the View menu in your report.)
Rationale. This is a statement of how the control should be implemented for the technology.
Evidence. The expected value and the actual value for the control on the host. The expected value is the value defined in the compliance policy. The actual value is the value returned during the last compliance scan on the host. These values are compared during the evaluation process for the control on the host, resulting in the Passed or Failed status.
See Control Values for information on the types of control values that may appear in your report, including integer values, regular expressions, and Windows permissions.
If an error occurs for a user-defined custom control, then a description of the error appears in the Actual field. For example, you might see "Error Code 2: Item not found" if the registry key that the control needs to check does not exist.
Extended Evidence. Extended evidence includes additional findings/information collected during the evaluation of the control on the host. For example, this may include results returned from queries made by the scanning engine when checking the control value. Extended evidence appears below the expected and actual values in the report.
Exception. When a host is exempt from a control, then exception details may also be included in the report. Exception details include the exception assignee, status, exception creation date and end date.
History. A history of user actions and comments for the exception on the host.