What Controls Are
A control in Regentra is an organizational requirement that maps to specific clauses, sections, or criteria within compliance frameworks. For example:- “Enforce Multi-Factor Authentication” might map to HIPAA § 164.312(d), SOC 2 CC6.1, and NIST CSF PR.AC-7
- “Maintain an Incident Response Plan” might map to HIPAA § 164.308(a)(6), SOC 2 CC7.3, and ISO 27001 A.16.1.1
Control Statuses
Every control has a status that reflects its current implementation state:| Status | Meaning |
|---|---|
| Not Started | No work has been done on this control yet |
| In Progress | Implementation is underway but not complete |
| Implemented | The control is fully in place and operational |
| Needs Review | The control was previously implemented but requires review — due to expiring evidence, policy changes, or a scheduled review cycle |
| N/A | The control does not apply to this organization’s environment |
FLAGGED_FOR_REVIEW, distinct from the implementation status on the control itself.
Controls default to Not Started when a framework is adopted. Updating statuses is how you track progress toward full compliance.
The Control Detail Page
Click on any control to open its detail page. This is where you do the actual implementation work.How to Satisfy
Each control includes a How to Satisfy section with practical guidance on what is required. This section explains:- What the framework requirement actually asks for
- Common implementation approaches
- What evidence auditors expect to see
Policy Documentation
Link relevant policies to the control. If you have a “Password Management Policy” that supports an access control requirement, attach it here so auditors can trace the connection.Implementation Notes
Free-form text field where you document how your organization specifically implements this control. Be detailed — this is what you will reference during audits.Evidence
Attach evidence that proves the control is implemented. Evidence can be:- Files — screenshots, configuration exports, signed documents
- Links — URLs to dashboards, monitoring tools, or external systems
- Automated signals — evidence pulled automatically from connected integrations
Assignment
Assign the control to a specific team member who is responsible for implementation and ongoing maintenance.Framework Mappings
The right sidebar of the control detail page shows Framework Mappings — a list of every framework requirement this control satisfies. If a control maps to three different frameworks, you will see all three listed with their specific clause or section references. This visibility is key for understanding how a single implementation effort contributes to multiple compliance programs.Cross-framework citations (NIST CSF, HPH CPG, HICP)
Below the Framework Mappings, each control card shows an Also referenced as panel sourced from the HHS/ONC SRA Tool v3.6.1. For every HIPAA §ref the control covers, the panel lists:- NIST CSF 2.0 subcategory IDs (e.g.,
ID.RA,PR.AC-7,DE.CM-7) - HPH CPG numeric references (Health and Public Health Critical Performance Goals)
- HICP Technical Volume references (Health Industry Cybersecurity Practices)
SRA Tool question reference
For each control whosehipaaRef matches a question in the HHS/ONC SRA Tool v3.6.1 workbook, the control card shows a collapsible HHS SRA Tool questions for §164.xxx panel listing every SRA question that probes that §ref. Each question renders:
- The question text and its
SRA-S{section}-Q{n}code - HHS’s
Required/Addressableflag (when present) - The full multi-choice answer set with HHS’s per-answer markers (✓ compliant per HHS, ! risk indicated, · skip)
Gap Analysis
The gap analysis view shows you where your compliance program stands and where the gaps are.Open gap analysis
Navigate to the Compliance Dashboard or select Gap Analysis from the sidebar. Choose a framework or view all frameworks.
Review gaps by status
Controls are grouped by status. Focus on Not Started and In Progress controls to understand your remaining work.
Prioritize remediation
Sort by risk level or framework criticality. High-risk controls and those that map to multiple frameworks should typically be addressed first.