About security history

These histories keep track of security-related events and changes to security-related properties. Separating security history from standard audit history draws attention to the importance of maintaining a secure system and prevents authentication events from overwhelming the audit trail.

Niagara 4.9 introduced security history. Similar to audit history, security history contains only security-related events, such as log-ins and —outs (authentication) and changes to security-related properties, such as changes to the properties that enable and disable secure communication.

The Security History Service provides the same properties as the standard History Service provides. You configure both sets of properties using the AuditHistoryService.

The station stores security-related property changes in both the security history and audit history logs. It stores authentication events only in a security history. This prevents frequent connection events from flooding the audit history.

Security facet

The Security History Service provides a facet labeled “security.” Wherever you can configure facets on a property, you can add this security facet to the property. Any user changes to the configuration of the property will generate a security history record.

Default security-related properties are those that appear on the security dashboard. The Niagara 4.9 release designates several frozen properties in the FoxService and WebService as security-related properties. These include:

  • FoxService: Fox Enabled, Foxs Enabled, Foxs Only Foxs Min Protocol, and Cipher Suite Group
  • WebService: Http Enabled, Https Enabled, Https Only Https Min Protocol, Cipher Suite Group, Require Https For Passwords and X Frame Options

To view security facets, open a component’s Slot Sheet. You cannot remove the security-related facet configured by default on a frozen property.