Administer > Audit and compliance > Audits, audit policies, and audit results

Audits, audit policies, and audit results

This section provides information about Audit Policies, and Audit Results.

Audits

An audit defines a set of rules or configuration values that determine whether the configuration of a managed server or group of managed servers matches your organization’s compliance standards. Audit rules can be configured in an ad-hoc manner or, more effectively, reference a predefined audit policy that specifically defines the required configuration for a managed server in HPE Server Automation.
An audit can:

  • Compare a server’s configuration against the rules defined in the audit policy.
  • Check that a configuration value meets the criteria specified in the audit rule.
  • Check to ensure that a specific value does or does not exist.

Some audit rules also allow you to run scripts that capture more detailed configuration information.

You can define the audit policy to:

  • Identify whether an IIS Metabase value exists, especially when you do not want it to.
  • Make sure a specific Linux service is set to always be running, especially if it’s a critical service that must always be running for security reasons.
  • Determine if a certain file system directory does not exceed a certain size limit.
  • Make sure that the maximum length setting for user passwords has not been exceeded.

You can define what the audit should look for, what values you expect to find on the server, and what replacement values to use that will fix them when differences are found.

After it is configured, an audit can be run once, scheduled for a future run, or be scheduled to run a regular basis. After an audit is run, its results indicate the extent to which those servers meet the definitions set in the audit rules. In cases where discrepancies are found, you can remediate those servers to bring them into compliance.

Audit Policies

An audit policy is a collection of reusable rules that define the desired state of server configuration, based on industry standards and the compliance goals set by your organization. An audit policy can be linked to audits, snapshot specifications, and other audit policies. When changes are made to an audit policy, all references to that audit policy are also updated.

An audit policy is typically created by a policy setter who understands the compliance standards that a company requires its servers to meet for a specific configuration domain and operating system. Administrators who manage servers can use predefined audit policies by linking them to their audits or snapshot specifications. If any changes are made to an audit policy, the audit that links to it also contains the updated rules. Administrators who audit SA managed servers can be sure their audits always reflect the latest policy standards in their organization.

Snapshots

A snapshot is a representation of the configuration state of a managed server, where the information was captured on a certain date, at a certain time of day. A snapshot is useful for capturing the configuration of a golden server that you would like to baseline compare against other servers in your facility. You can use the snapshot as the source of an audit. If a server does not match the configuration captured in the snapshot, you can remediate those servers after the audit has run.

Compliance and remediation

The Compliance view in the SA Client allows you to view the overall compliance levels for SA managed servers in your facility. The Compliance view is also known as the compliance dashboard. From the compliance da