As a security feature, Klocwork allows the Klocwork administrator to control who will have access to Klocwork, and to what software projects. During installation, the Klocwork installer chooses whether or not to enable this security feature and decides if it should be associated with an existing NIS or LDAP server.

With NIS and LDAP integration, the administrator will use your organization's identity server to choose names of individuals and groups who can access projects in Klocwork.

By associating permissions with the individual's computer user ID (or the common name presented by the directory server), the Klocwork administrator can give permission to individuals or groups to:

• Create and delete projects
• Build a project
• View projects
• Start and stop the Klocwork Servers
• Assign specific roles to limit access to status changes

The Klocwork administrator can also give individuals the ability to be a team leader and assign permissions.

To leverage your initial success with Klocwork, you can expand your use of the product for issue and vulnerability detection. This may involve expanding the number of developers using Klocwork and/or beginning additional pilot projects with other software teams or business units. You can also increase the number of potential defects and vulnerabilities that Klocwork detects by repeating Phase I, Stage 6.

Several different APIs are available to create new rules with Klocwork:

• Metric thresholds are available, with the ability to create any compound metric using any of Klocwork's 100+ metrics. See Changing the thresholds for reported metrics and Customizing metrics reports in Klocwork Static Code Analysis.
• APIs for the creation of new checkers are provided with Klocwork as well.
• See Coding standards mapped to Klocwork checkers, for a list of Klocwork checkers that can be used to enforce industry coding standards.
• See Integrating with Structure101 for a description on using Klocwork and Structure 101 to enable architectural enforcement for your codebase.

Klocwork Professional Services can be retained to help with any of these tasks.

Many organizations choose to integrate Klocwork data into an existing Defect Tracking System, such as IBM Rational ClearQuest, Perforce, Bugzilla, GNATS, and others.

Klocwork issues discovered during integration build analysis can be used to generate Problem Reports in an existing Defect Tracking system. This enables Klocwork issues to be managed and tracked by the same tools used by development, QA and other parties involved in the SDLC.

A unique capability of Klocwork is that a link from Klocwork Static Code Analysis can be added to a Problem Ticket, providing an easy way for a developer to analyze and fix the issue without having to re-enter the information into the Problem Reporting system.

This integration is typically achieved by using a report from Klocwork Static Code Analysis as an input to a script that generates the Problem Ticket, complete with a URL link to make it easy for developers to understand and fix the reported issue.

You can configure the Klocwork Server for email notification, allowing your developers to receive emails whenever a new issue appears after a system build or when a new issue is assigned to them.

By default, each user profile in Klocwork Static Code Analysis is configured to receive email notifications, but developers can turn emails on and off.