Security Analyst Terminologies

Term

Description

Security Tag

  • Metadata tag that you apply to a device configuration template to indicate that the template contains security features.

  • Security Tags have no effect on the Streamline NX templates and are used for reporting purposes within the Security Analyst console only.

  • You can create any custom tag you want within Security Analyst, and then apply it to one or more templates in the Security Templates screen.

  • You can assign a single tag to a template, or multiple tags as needed.

Template

  • Device configuration templates created in Streamline NX used to configure multiple devices at a time.

  • Security Analyst displays all SLNX templates in the Security Templates screen (regardless of whether the template contains security features or not).

  • There are two ways to create configuration template. Create template via Standard Device Preferences (SDP) or from Extended Device Preferences (XDP).

  • You can view the list of device configuration templates and apply security tags within Security Analyst, but you can only edit the templates in the Streamline NX Management Console.

Security Template

A device configuration template that is assigned at least one Security Tag in Security Analyst.

Task

A configuration task created within Streamline NX that designates templates to apply, the devices to apply it to, and when the task is applied (i.e. on a repeating schedule or only once).

Policy

A device configuration template that has been tagged with one or more security tags. Together, the combination of a configuration task and a tagged template is referred to as a ‘policy’.

Policy Applied vs. In Policy vs. Out of Policy

  • When there is no previous successful applied policy and the tagged template result to success achieved via ‘apply’ action, the device status is considered ‘policy applied’.

  • From a previous state of ‘in policy’ or ‘policy applied’, a device is considered ‘in policy’ when tagged template applied on the device achieved either via ‘apply’ or ‘check’ action reports as successful with “Match” result.

  • If a task fails at either the ‘check’ or ‘apply’ action for a tagged template, devices covered by the policy are considered ‘out of policy’.

Coverage

Reports the percentage of devices/servers to which a tagged security template has been applied.