Features

Hyperproof has the following core features:

Health

The health of your program is determined by the health of its controls. If your controls are healthy, your program is healthy. Hyperproof comes with default health settings that work for most organizations, however these settings can be customized.

Freshness

Freshness is a status set on a control that indicates whether the control activity was last performed within the time frame assigned for that particular control or whether the control activity was last performed outside of the designated time frame. If a control is fresh, it’s healthy. When you turn on freshness for a control, you define its expiration period at the end of which its freshness status will automatically change from Fresh to Expired.

Automated evidence collection

Automated evidence collection (Hypersyncs) eliminates the manual process of searching for proof, filing it away, and having to remember to gather the latest version of proof prior to an audit. Connecting to an external service app—such as AWS, Azure, or GitHub—via a Hypersync allows you to collect proof when that proof is a report or log file generated by those external service apps.

Integrations

Hyperproof integrates with a number of external cloud-based productivity apps such Drive and Slack. Integrations allow for uninterrupted collaboration by using the tools you already use on a daily basis.

Custom fields

One way to customize Hyperproof to fit your organization’s unique needs is by utilizing custom fields. A custom field can be anything from department names to numbers, and can be applied to controls, labels, requests, requirements, risks, vendors, or tasks.

Scopes

This additional Hyperproof purchase provides a mechanism for breaking individual controls down into child controls based on combinations of categories that identify specific sectors of your organization.

Organizations with product lines, regions, and subsidiaries—to name a few—can use the scopes feature with custom fields to determine if the proof collected across the different scopes satisfies the parent control’s requirements.