Objects

The following objects are found in Hyperproof:

Programs

All of the work you do in Hyperproof happens in your organization. Think of it as the highest level within the Hyperproofhierarchy. A program is where you manage and track all activities for a particular regulatory or industry standard, like SOC 2 or ISO, or a homegrown compliance framework.

Requirements

Programs are made up of requirements that represent the contents of the laws and standards on which the programs are based, and are not editable in Hyperproof. You may have also encountered or used other names for requirements, such as criteria and control objectives. Requirements often have fields defined by the framework’s managing authority. Hyperproof calls these fields details. These details describe if and how a requirement is met. This is different than a control being designated as healthy as requirement details represent the collective state of all related controls to pass an audit or assessment.

Controls

Controls describe the manner in which your organization intends to comply with requirements, such as by implementing processes, procedures, activities and/or tools. Typically, you will have one or more controls for each requirement. Some organizations define controls as the smallest subset of processes needed to meet a particular requirement, while other organizations might define a single control as a multi-step or complex process. With Hyperproof, organizations have the freedom to define controls as they see fit. For organizations that prefer an out-of-the-box solution, Hyperproof offers illustrative controls for each of the frameworks it supports.

Proof

For many, if not all, requirements, you’ll need to provide evidence of compliance. Hyperproof simply calls this proof. This typically takes the form of files and documents such as data log files, screenshots, meeting notes, etc. Users link the proof they collect to the appropriate controls.

Labels

Labels are a way to organize, manage, and reuse proof in Hyperproof. Think of labels as folders that are dedicated to certain pieces of proof.

Issues

Issues are available on every major Hyperproof object. They allow you to keep track of any findings you discover and can be remediated with tasks.

Evaluations

Evaluations are found in the Assessments module. You'll use evaluations to assess your program's controls and requirements, as well as keep a record of your findings.

Requests

Requests are found in the Audits module. You'll use requests to task a team member with providing proof for a specific audit period.

Tasks and repeating tasks

Tasks are used to ask members of your team for proof, as well as to remind you of a particular activity that you need to get done. For routine tasks that happen over and over, you can automate the process by setting up a repeating task that repeats based on a schedule or an event.

Risks

A risk is the potential damage an organization may face if they fail to comply with industry standards, laws, and regulations. Risks can cause financial, legal, reputational, or even criminal repercussions. You'll manage your organization's risks in the Risk Register module.

Vendors

Vendors provide organizations with goods or services that allow them to run their businesses. Your organization may work with dozens or even hundreds of different vendors. You'll keep track of your vendors in the Vendor Register.