Skip to main content

Understanding the Related Tab: How Monitors Map to Controls and Evidence

Learn how each monitor supports your compliance program.

J
Written by James Fletcher
Updated over a month ago

Understanding the 'Related' Tab in a Monitor

The Related tab helps you connect the dots between a specific monitor and the broader compliance obligations it supports. This view provides traceability — so you know exactly how a monitor contributes to your audit.

Here’s what you’ll find in this tab:


Related Controls

This section lists the compliance control(s) that the monitor supports. Controls define the technical or procedural requirements you must meet under frameworks like SOC 2, ISO 27001, or PCI DSS.

  • For example, a monitor mapped to: CTRL-9 – Privileged User Accounts

    • This indicates that the monitor checks for proper configuration of user & service accounts, which relates to limiting privileged access — a common control area across frameworks.

You can click “Go to Controls” within the panel to view details about the mapped control, including its requirements, documentation, and any assigned owners.


Related Evidence Requests

This section will only appear if you have an open audit. It shows which evidence request(s) the monitor is tied to in your audit program. These are the specific requests your auditor will review during fieldwork.

  • For example, a monitor mapped to: ER-41 – Privileged Access to the Cloud Console

    • his indicates that the monitor can be used as part of the evidence for this request, reducing the need for manual exports or screenshots.


Why It Matters

  • Traceability: Know exactly which requirement(s) a monitor helps you meet.

  • Audit readiness: Confirms that the evidence collected will satisfy real auditor requests.

  • Ownership: Makes it easier for control or evidence owners to stay aligned with what’s being monitored

Did this answer your question?