Linked objects within a program
Within a program, you'll find linked objects like requirements, controls, and labels. When you click into that program, you'll find tabs at the top that you can click into to manage these objects.
Click the arrows below to learn more:
Requirements
Requirements
Overview: Each Program is made up of Requirements, which represent the specific content and obligations dictated by laws and standards.
Function: Requirements detail what needs to be achieved to meet compliance, providing a basis for implementing Controls and gathering Proof.
Next to the details tab at the top, we can see the requirements tab. In this tab, we can view and manage your program’s requirements. Along with viewing requirements, you can also link controls to requirements, add proof, create tasks, change the status, and add related requirements.
Controls
Controls
Overview: Controls are mechanisms implemented to ensure compliance and manage risks. They can include processes, procedures, activities, or tools.
Function: Controls help track and reduce risks, ensuring that compliance requirements are met effectively. Programs may contain multiple Controls tailored to different Requirements.
Following the requirements tab we have next to the controls tab. Think of this tab as a filtered view of your controls. On this tab, you are viewing just the controls on this program (including any you have linked). Along with viewing, you can also manage and click into controls from this area as well as import additional controls.
Here's an example of illustrative controls within a program.
Labels
Labels
Overview: Proof, or evidence, refers to the documentation and data that demonstrate compliance. This can include data logs, meeting notes, screenshots, and CSV files.
Function: Proof is linked to Controls to validate compliance. It can be imported from various sources and is essential for audits and assessments.
Next to the controls tab is the label tab. When you add a label to a control it will show in this list here. This is a list of all the labels on your program. From here you can view and manage the labels in your program.
Here's an example of Labels within Hyperproof.
Program requirements
The requirements tab allows you to view and manage your program’s requirements. In this area, we can view requirements individually or in the grid view. We can also add proof directly to a requirement, change the status of our requirements individually or through bulk selection, and leverage crosswalking to link additional controls from one program to another.
We'll discuss this area in this video tutorial, as well as explain further how crosswalking works in Hyperproof.
The tutorial below is shown in the administrator role with organizational permission as a manager in Hyperproof. If you are in another role in Hyperproof or have a different permission, you may not have access to some of these areas shown, or they may be greyed out.
Leveraging crosswalks
Hyperproof has built-in crosswalks based on the Secure Controls Framework (SCF). The framework currently incorporates over 850 controls, is baselined across more than 150 regulations and standards, and is regularly updated.
When you utilize Hyperproof’s crosswalk feature, you become more efficient in managing your various compliance projects. Because you’ll have already done most of the work in one program, you’ll only need to collect proof for a smaller set of controls, saving you and your team hours or a week's worth of work.
Crosswalking
Crosswalks help you eliminate repetitive work by identifying common requirements across multiple compliance frameworks. For example, let’s say you already stood up an ISO 27001 program and now you want to stand up a SOC 2 program. Hyperproof examines the requirements in both programs and then maps requirements found in your ISO 27001 program to your SOC 2 program. Hyperproof calls these mapped requirements related to requirements.
How do crosswalks work?
In the video above, we saw when we clicked on a requirement we could access a controls tab that allowed us to link our controls from one program to another, based on suggested related requirements. This allowed us to leverage the crosswalking feature in Hyperproof to link a control between multiple programs.
Click the arrows below to learn more:
Linking controls to a requirement
Linking controls to a requirement
Click on a program
Click on the requirements tab.
Click on a requirement.
Click on the control tab.
Click link controls.
Selecting controls
Selecting controls
Select necessary controls to link
Like controls will be brought to the top with a green banner.
Click link selected controls.
Reuse program dashboard
Reuse program dashboard
Once controls are linked they will show up on the reuse section on the program dashboard.
Program controls tab
View and manage the controls in your program on the controls tab. This tab shows all of the controls that are a part of this program only, including the ones that we have linked. Think of it like a filtered view of just the controls for the specific program you are clicked into!
In this video, we'll click into this tab and go over the different views, and filter tools, and talk about navigation when selecting a control from this area.
The tutorial below is shown in the administrator role with organizational permission as a manager in Hyperproof. If you are in another role in Hyperproof, or have a different permission you may not have access to some of these areas shown or they may be greyed out.
Program labels tab
The labels tab within a program allows you to view and manage the labels in your program. This tab shows all of the labels that have been applied to the controls within your program. Think of it like a main list of your labels in that program. You can also manage all of these labels in this area.
In this video, we'll click into this area and discuss how you can manage the labels on your program.
The tutorial below is shown in the administrator role with organizational permission as a manager in Hyperproof. If you are in another role in Hyperproof, or have a different permission you may not have access to some of these areas shown or they may be greyed out.
Since our last update in March 2025, if you have a Hypersync on a label you can now create a test easily on your control if you link that label that has a Hypersync to your control. We recommend this as a best practice, so keep this in mind when setting up your organization.
Working with issues
In order to pass the audit, issues need to be remediated. Because remediation can take several steps, visibility of progress is absolutely vital.
Remediation can range from a quick fix to a multi-quarter project that needs to be tracked. At best, issues mean spending resources to fix a problem. At worst, they jeopardize a company’s entire future—losing a certification can mean not being able to do business at all. Because many organizations don’t discover issues until the audit is in progress, they are oftentimes left scrambling under severe pressure to implement a fix.
Because Hyperproof is a continuous compliance operations platform, issues can be discovered and addressed long before your organization enters its audit phase.
Click the arrow below to learn more:
Creating an issue
Creating an issue
From the left menu, select the tab that corresponds with the issue you want to link. For example, if you want to link an issue to a control, select the Controls tab.
Select the specific object. For example, if you want to link the issue to control ID 1234, select that control.
Select the Issues tab.
Click New.
Enter the following information:
Summary (required) - A summary of the issue and the potential result if it isn't remediated
Description - A detailed overview of the issue
Make issue private checkbox - Select this checkbox to make the issue private. Doing so restricts inheritance—only users explicitly added to the issue’s facepile can see the issue. Other users (such as members of affected objects) can see that the issue exists, but they’ll only see the issue ID. To access the issue, they’ll need to contact the issue manager(s).
Action plan - The plan to remediate the issue
Impact - The impact the issue has on your organization if it isn't resolved
Priority - The priority level for resolving the issue
Assignee - The individual who will work to remediate the issue
Effort level - The amount of effort it'll take your organization to remediate the issue
Business owner - The individual who owns the issue. Note that a contact can also be an owner.
Executive sponsor - The individual who is of senior level and ultimately responsible for overseeing the remediation of the issue
Due date - The date that the remediation is due
Discovered on - The date that the issue was discovered
Click Create.
The issue is created.
Affected objects on issues
It's important to monitor the linked affect objects on issues. In the tutorial below we'll walk through why this is the case, especially when it comes to our controls and the health of those controls.
Note, that the below tutorial shows the example with an issue on a control but issues can also be linked to Programs, and when clicked into a program you also will find an issues tab.
The tutorial below is shown in the administrator role with organizational permission as a manager in Hyperproof. If you are in another role in Hyperproof, or have a different permission you may not have access to some of these areas shown or they may be greyed out.
Click the arrow below to learn more:
Linking an additional affected object to an issue
Linking an additional affected object to an issue
From the left menu, select the tab that corresponds with the issue.
For example, if you want to link an additional affected object to an issue that's linked to a control, select the Controls tab.
Select the specific object that the issue is linked to.
For example, if the issue is linked to control ID 1234, select that control.
Select the Issues tab.
Select the issue.
In the right pane, click the arrow in the Link button next to Affected objects.
Select either Link new or Existing link.
If you select Link New, the Create New window opens. Select an object from the drop-down menu, name the object, and then click Create.
If you select Link Existing, the Link Objects window opens. Select the object or objects you want to link, then click Link.
The affected object is linked.
