Note: The information below is shown for an administrator role. If you have another role in Hyperproof, like compliance manager, user, or limited access user, your access may be limited due to your organizational role and object-level permissions. We recommend viewing the organization roles and permissions article and object roles article to learn more about permissions.
Within Hyperproof, there are different items that we refer to as objects. These objects are significant because they are the foundation of Hyperproof. We refer to them as objects because they have one-to-many relationships.
Objects in Hyperproof
Programs: Hyperproof has many supported compliance framework templates, but you can also create a unique program template for your organization.
Requirements: Programs are composed of requirements that represent the content of the laws and standards on which they are based.
Controls: Controls help keep your organization's compliance efforts on track by helping to reduce risks. Your program may have hundreds of controls depending on your organization's needs.
Proof (evidence): Proof or evidence—as it's called in Hyperproof—can be anything from data logs and meeting notes to screenshots and CSV files. You can import proof in different Hyperproof areas, including from the main navigation menu and via controls.
Labels: Labels are designed to help you organize and manage proof. Without labels, you would have hundreds, or even thousands, of pieces of proof floating around Hyperproof.
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 them to assess your program's controls and requirements and record your findings.
Requests: Requests are found in the audits module. You'll use requests to assign a team member the task of providing proof for a specific audit period.
Programs provide the framework, requirements detail compliance obligations, controls implement measures to meet these obligations, proof serves as evidence of compliance, and labels help organize this evidence.
By effectively understanding and using these objects, you can enhance your organization’s compliance efforts and maintain a well-structured and efficient compliance program.
Hyperproof workflow
All of the work you do in Hyperproof happens in your organization. Think of it as the highest level within the Hyperproof hierarchy.
The video below covers the modules, features, and objects within Hyperproof. These features are important to understand how your organization will work within Hyperproof.
Click the arrows below to read more about the Hyperproof workflow.
Programs
Programs
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. 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 differs from a control being designated as healthy because requirement details represent the collective state of all related controls to pass an audit or assessment.
Controls
Controls
Controls describe how your organization intends to comply with requirements, such as by implementing processes, procedures, activities, and/or tools. Typically, you have one or more controls for each requirement. With Hyperproof, organizations can define controls as they see fit. For organizations that prefer an out-of-the-box solution, Hyperproof offers illustrative controls for each framework it supports.
Proof and labels
Proof and labels
For many, if not all, requirements, you need to provide evidence of compliance. Hyperproof 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 are a way to organize, manage, and reuse proof in Hyperproof. Think of labels as folders that are dedicated to specific pieces of proof.
