Allowed Items

An Allowlist is a list of items that comply with industry, regulatory, or organizational standards. See Types of Allowlists for more information. Each permitted item on an Allowlist is referred to as an Allowed Item. Tripwire State Analyzer uses a different Allowlist for each Allowlist Type (open ports, services, user accounts, etc.) it monitors.

On the Allowed Items page, there is a tab for each Allowlist Type that TSA monitors. You can configure TSA to show or hide these tabs from the Display Types tab of Allowlist Settings.

  • Each row represents a different Allowed Item.
  • Items with a NEW label were created recently. The time to display the label can be configured on the Allowlist Settings Preferences tab. The default time is 24 hours.
  • Click on an Item to see more details about it.
  • Use the icons above the table to import or export Allowed Items from an external file, show and hide columns, or filter the Items displayed.

You can also see the history of changes for each Allowed Item, compare versions over time, and restore a previous version.

Working with Allowed Items

From the Allowed Items page, you can create a new Allowed Item or modify an existing one.

Managing Software Allowed Items from a Patching Solution

If you have integrated TSA and a patching solution (see Integrating TSA with a Patching Solution in the Tripwire State Analyzer Administration Guide) you can manage the allowed and recommended versions of Software Allowed Items from the Software tab.

To do this, you first create new Allowed Items based on software detected by the patching solution. Then you can manage the allowed and recommended versions of those Allowed Items to make sure that only approved versions are allowed.

Tracking Changes in Allowed Items

Tripwire State Analyzer tracks changes to an Allowed Item by creating a new version each time the Item is changed. Allowed Items can change when they are directly edited in TSA, or when they are exported to a CSV file, edited externally, and then re-imported.

On the Allowed Items page, you can view all of the historical versions of an Allowed Item, compare two versions of the same Item, or restore an Allowed Item to the state of a previous version.

Note:  

Allowed Item versions in TSA are different from element versions in Tripwire Enterprise. Restoring or modifying Allowed Item versions in TSA has no effect on the element version data stored in TE.

Importing or Exporting Allowed Items

You can export Allowed Items to CSV, PDF, or JSON files. You can also import CSV files, supporting a workflow where you export Allowed Items to a CSV file, make edits externally, and then import them back into TSA.

Tip:  

From any Allowed Items tab, you can only import or export Items for that Allowlist Type (although multiple files can be imported at once).

From the Display Types tab of the Allowlist Settings page, you can import or export Allowlist Items for multiple Allowlist Types at once.

Types of Allowlists

Allowlist Type

Description

Group Memberships

A group membership is a pairing between a user group and a member of the group (i.e., a sub-group or a user account).

Open Ports

An open port is a listening TCP or an open UDP port on a monitored system. Each open port consists of a communication protocol, port number, and the associated process (for example, SSH).

Agent-based allowlisting queries the monitored system for port records, whereas Agentless allowlisting uses port information collected from an external scan.

If your TSA environment employs Agent-based allowlisting on a Windows monitored system and the process name is svchost.exe, TSA will also capture the associated service name(s).

For Agentless allowlisting, the process name shown in TSA is determined by the choice of tool that performs the scan. For example, Nmap uses the nmap-services file to map a port number and protocol to a process name.

Routes

A route is a network-accessible path from a monitored system to a host or network. Each route consists of a host or network, the netmask (or subnet mask) of the host or network, and the gateway through which the monitored system accesses the host or network.

On monitored systems running a Windows operating system, TSA captures IPv4 non-default persistent routes.

On monitored systems running a RHEL (Red Hat Enterprise Linux) operating system, TSA captures IPv4 active, non-default routes that use a gateway (not directly connected).

Services

A service is a software application that runs as a background process on a monitored system.

On monitored systems running a Windows operating system, TSA queries all services that do not have a status of ‘Disabled.’

On monitored systems running a Unix-compatible operating system, TSA queries any running service.

On monitored systems running a supported Linux platform, TSA queries the running SysVinit, Upstart, xinetd, and systemd services (if available).

Shares

A share is a permission(s) applied to a user account or user group that grants access to a shared directory.

Software

A software item is an application, patch, or utility on a monitored system. However, it is possible to also include scripts, firmware, portable applications, and other software that does not register with the operating system using the custom software feature.

Users

A user is a user account with access to a monitored system. Each user consists of a username, the age of the password (in days), enabled/disabled status, and an optional last-login timestamp.