Documentation Nexus IQ Server 1.19

You configure the Audit and Quarantine features by adding them to Repository Manager as a plug-in capability.

To configure Audit and Quarantine:

At this point, an audit of the selected repository is automatically started. Repository Manager contacts IQ Server and evaluates the components within the selected repository against any associated policy. The results are displayed in Repository Results, which is described in the next section.

After the IQ: Audit and Quarantine capability is added, it appears on the Capabilities tab in Repository Manager as shown in the figure below.

To disable Audit and/or Quarantine:

To re-enable Audit and/or Quarantine:

The creation, modification, and deletion of repositories is managed via Repository Manager. However, when connected to IQ Server, informational details of the repositories are also available.

To view these details:

Details on repositories include:

Clicking the Delete button (shaped like a trash can) allows you to delete the repository after you confirm the deletion in a dialog.

Repositories, which appears in the sidebar of the Organization & Policy area, lets you set security for repository evaluation results. The process is the same as managing roles and permissions for organizations and applications on IQ Server. Through role assignments, you have the ability to grant users different permissions for repository evaluation results without granting them access to organizations and applications. For example, to grant a user the ability to view repository results, you assign the user to a role with View CLM Elements permission. To edit repository results, you assign the user to a role with Edit CLM Elements permission. The role assignments affect all repositories, not individual ones. For more information about assigning user roles, see Role Management in the Security Administration chapter.

Once the Audit and Quarantine features are enabled, whenever you add a component to a proxy repository (or delete one), Repository Manager contacts IQ Server to evaluate the components within the proxy repository against any associated policy. The IQ Policy Violations, are summarized in Repository Manager, and detailed in IQ Server.

In Repository Manager:

The audit results are summarized in the IQ Policy Violations column of the Repositories tab as shown in the figure below.

The IQ Policy Violations column includes the following items:

In IQ Server:

The IQ Policy Violations column will also alert you if there are any errors in the audit and quarantine process. If there is an error, for example if Repository Manager cannot communicate with IQ Server, a red exclamation mark will appear to the right of the Repository Results link along with text pertinent to the error that occurred. Additional information will be available in the Repository Manager logs.

If you have permissions to add capabilities in Repository Manager, then you can also access Repository Results from the Capabilities tab:

Both methods open Repository Results on IQ Server as shown in the figure below.

Repository Results is a display of policy violations and the components that violated those policies, as well as components that don’t have violations. At the top of the view is a summary section with the following information:

Below the summary section is a list of policy violations and the components that violated those policies. By default, this information is ordered by the highest policy threat level. You can refine the list using one of the following filter categories:

When you select a component listed in Repository Results, more detailed information is provided in the Component Information Panel (CIP) section of Repository Results.

Component Info

The Component Info tab displays the following information about a specific component:

Policy

The Policy tab displays all policies that were violated by a component. Here you can see the name of the policy that has been violated (and any action that was taken), the name of the constraint that has been violated, and the value that was found.

While the Policy/Action and Constraint names are straight forward, the Condition Value may be a little confusing at first. A condition is simply the if part of an if/then statement. If a certain condition value is found which is equivalent to a condition being met, then the policy will be violated. E.g. if we have a policy that has a condition such that if a security vulnerability is found, our Condition Value column would indicate, Found x Security Vulnerabilities. In the same regard, Constraints are simply multiple conditions joined together.

Licenses

The Licenses tab displays all Effective licenses, any licenses identified as declared by the author of the component, as well as any license found during the scan of the component source code. It also allows you to override the Effective license. To do this:

Labels

The Labels tab displays any component labels that have been assigned previously at the root organization level on IQ Server. Component labels are essentially metadata that is assigned to a component within the context of a particular application or organization.

Assigning a Label

When assigning a label, you will only see labels defined on the root organization.

To assign a label:

When applying a label, you have the following options:

Vulnerabilities

The Vulnerabilities tab displays all security vulnerabilities related to a component. The list of vulnerabilities is sorted by Threat Level from higher to lower risk. The Problem Code column displays unique identifiers obtained from security information web sites such as CVE and OSVDB. The Info button provides additional information about each security vulnerability. Lastly, the Status column tracks the state of your research regarding the vulnerability.

Policy violations for components found in your repositories can be waived with a number of options for the scope and target of the waiver. As with all features, make sure to verify you have the appropriate level of access provided by the role you have been assigned.