# Regulatory Compliance

Track each requirement's validations, policies and evidence against CMMC or your own standard, and see what is due.

When the record of a CMMC assessment lives in spreadsheets, binders and email, nobody can say on a given day what is overdue, which regulation asks for what, which policy states a rule, or what the SPRS score really is. At Acme Precision, the security officer keeps it all in Regulatory Compliance: every requirement with its due dates, the regulations behind it, the scores, the policy library, the evidence records and the reports an assessor asks for.

[Add it from the Marketplace](/tenant/?open=settings/marketplace)

## What it does

Regulatory Compliance keeps your compliance record for a framework. CMMC Levels 1, 2 and 3 are available now, and you can build a custom standard of your own. Each requirement is checked again on its own schedule. You record whether it was met, and the module works out what is overdue, the POA&M (plan of action) and the SPRS score from those records. Nothing is typed in by hand.

A register of regulations shows what each law, standard or policy set covers, worked out from the links you already keep. Evidence is kept as records: one report, statement or captured activity that answers the objectives of one or more requirements.

**Regulatory Compliance** in the sidebar opens these pages:

- **Compliance**: what is due. It opens on the **Due** view, a list of every requirement grouped **By family** or **By urgency**, with a **Find** box and filters. **Calendar** switches to a month-by-month grid of every review period.
- **Policies**: the policy library, with published versions, review dates, the requirements each policy states and review notes. The **Policy approvals** tab holds changes waiting for a decision.
- **Evidence**: what to collect and where it comes from. **Records (what to collect)** lists each evidence record with who collects it, how often and how it is proven; **By system** lists every evidence source.
- **Regulations**: the register of authorities, such as NIST, 32 CFR, DFARS, FAR and ITAR, and your own policies, with the items under each and what each one covers.
- **Forms**: the blank forms people sign, with the PDF and the Word file each was made from.
- **Diagrams**: network, boundary, data flow and workflow drawings.
- **Responsible parties**: the role titles that own evidence, forms and policies, who holds each, and how to reach them.
- **Frameworks**: the frameworks and systems set up, and custom standards. Administrators only.
- **Reports**: the **Compliance dashboard**, the **POA&M report** with the SPRS score, the **System Security Plan**, the **Policy coverage report** and the stakeholder reports.
- **Access recertification**: shown only to the people who decide the periodic access review.

Click a requirement to open it in a side panel: its official statement, its lettered assessment objectives (for CMMC), how often it is checked, its validation history, the policies that state it and its System Security Plan narrative.

The module comes with a sample standard, **SAMPLE — Internal Security Review**, with six requirements, so the calendar has something to show before you set up a real framework. You can archive or delete it from **Frameworks**.

## Set it up

A Workspace Admin does this first.

1. Open **Frameworks** and click **Set up framework**. Pick the framework and level (for example **CMMC Level 2**), then work through the steps across the top with the button at the bottom right: name the **System** being assessed and who is responsible for it, build its **Asset inventory** from People, Technology, Facilities and External Service Providers (**Add from Assets module** copies in assets you already keep), and categorize each one. Click **Finish setup**. Setting up the scope does not change your records in the Assets module.
2. Open **Responsible parties** and click **New responsible party** for each role that owns evidence, forms or policies, such as *CUI Data Owner* or *IT Manager*. Fill in the **Title (the role, not the person)** and what it is **Responsible for**. Add the role's own contacts if it has them: **Role email** (a shared mailbox), **Role phone** (a support or on-call line) and **When and how to reach the role**. Under **Held by**, tick who holds it. Click **Save**. Responsibility goes to the role, never to a named person, so a staff change is made in one place.
3. Add your policies on **Policies** with **New policy**, and add your blank forms on **Forms** with **New form**.
4. Add your evidence records on **Evidence** (**Records (what to collect)** view, **New record**).
5. Open **Module Settings** from the ⋮ on the **Regulatory Compliance** sidebar row. On **Configuration**, choose the approver roles: the people who may approve policy changes. On **Preferences**, check **default_cadence_months** (how often a requirement is reviewed when the framework suggests no cadence, 12 by default), **upcoming_horizon_days** (how far ahead counts as due soon, 30 by default) and **cui_data_owner** (the label shown for whoever answers for CUI requests). See [Module settings and versions](article:fb7c92e4-6dcc-4ef4-80bc-1b6e7482e540).
6. Give the permissions to your own roles, such as Security Officer or Policy Approver. See [Users and roles: create and edit roles](article:88d4e232-d5b8-4909-b452-cfe96d3d550f).
7. If you use the access recertification or count Work Orders as evidence, subscribe to Work Orders too, and mark the CUI owners on their People records in Assets.

How to reach each holder comes from their own contact details (job title, work phone, mobile and when they are available), which they set in My profile or a Workspace Admin sets under **System settings**, **Users**. Someone who holds a role but has no login can be named with a phone number instead.

## See what is due

1. Open **Regulatory Compliance** from the sidebar. It opens on **Compliance**.
2. If more than one system is set up, pick yours in the drop-down at the top left.
3. Read the tiles: **Overdue**, **Due soon**, **Coming up**, **Objectives not met**, **Never assessed**, **Frequency to define** and **Requirements**.
4. Each row shows the requirement's code and title, how often it is checked, when it is due and its status, such as **OVERDUE** or **IN WINDOW**. Click the arrow at the start of a row to show its objectives, or use **Expand all** and **Collapse all**.
5. Click **By urgency** to put what is overdue first. **On track** is folded; click **Show** to open it. **By family** groups the requirements by area again.
6. Type a code (3.1.20), a few words or a crosswalk reference in **Find**. To see only objectives evidenced one way, pick it in the evidence filter next to it. **All owners** narrows the list to one responsible party.

## Read the calendar

1. On **Compliance**, click **Calendar**.
2. Each bar is one review period. The key along the top explains the colours: **Upcoming**, **In window**, **Due soon**, **Overdue**, **Missed**, **Validated late**, **Done**, **Not met** and **Ad-hoc**. Click the **i** at the right of the key for the full rules.
3. A missed period stays red even after you catch up, because the gap is part of the audit trail.
4. Use the arrows to move through time and **Today** to come back. Pick **Days**, **Months**, **12 mo rolling** or **Years** in the range picker.

## Open a requirement

1. On **Compliance**, click a requirement row or its **Assess** button (**View** if your role cannot record).
2. Read the statement, the action that proves it and the evidence expected. **How often** shows its schedule; **edit** changes the schedule (administrators).
3. For CMMC, read each lettered objective under **Assessment objectives** with its status and **Owners**. Click the **i** after an objective for **What to collect**, and **Policies & evidence** to see the policies and evidence sources behind it.
4. Scroll down for **Validation history**, the policies that state the rule, and the **Implementation narrative (System Security Plan)**.

## Record a validation

1. Open the requirement and click **Record validation** (on a CMMC requirement, on the letter you checked).
2. Pick the result: **Met**, **Not met** (a deficiency) or **Not applicable**.
3. For **Not met**, fill in the plan of action: **Milestones**, **Responsible party**, **Resource estimate** and **Scheduled completion**. It becomes an open POA&M item until a later validation records **Met**.
4. Write what was done or proven in **Notes**. On a CMMC objective, tick how it was checked (**Examine**, **Interview**, **Test**) and the evidence relied on.
5. Set **Performed on** to the date the check happened, pick what it **Applies to** if it was one facility or asset, and attach the evidence files.
6. Click **Record validation** (on a CMMC objective, **Save & next** or **Save and close**).

To record many policy objectives at once, pick **Policy objectives: a document states it** in the evidence filter next to **Find** and click **Record policy objectives**. Click **Read** on each row to read the policy section that states it, tick the ones you have read, and click **Record ticked as met**.

## Create a custom standard

1. On **Compliance**, click **Custom standard**.
2. Fill in a short **Code**, a **Name**, the **Authority** and a **Description**.
3. Click **Create standard**.
4. Click **Requirement** to add each requirement: its code, title, parent group, the action that proves it and its schedule (one-time with a due date, or every so many days, months or years).

## Keep the regulations register

1. Open **Regulations**. Pick the system in the drop-down at the top; the counts are for that system.
2. Each authority (**NIST**, **32 CFR (CMMC program)**, **DFARS**, **FAR**, **ITAR**, **ATF** and **Our policies**) lists its items, such as **NIST SP 800-171 Rev 2** or **DFARS 252.204-7012**. **Covers** shows how many requirements, policies and evidence sources answer to each one.
3. Click a regulation's name to see the **Requirements that cite it**, the **Policies** that follow from them and the **Evidence** that answers to it.
4. To add one of your own, such as a section of ITAR or a state law, click **Add a regulation**. Pick the authority it goes **Under** (or a new authority), type the **Name**, a **Citation or description**, a **Link** and **Notes** on how it applies to you, and click **Save**.
5. Use the pencil to add a citation, link or notes to any item. Built-in items keep their names and cannot be removed; one of your own can be removed once no evidence source names it.

What each regulation covers is worked out for you: a requirement cites the regulations in its references, a policy follows from the requirements it is linked to, and an evidence source answers to its requirement's regulations plus any it names itself.

## Read and print a policy

1. Open **Policies**.
2. Search by code, title, owner, requirement number (3.1.1) or words in the text, and narrow the list with **All families**, **All types**, the status filter and **All responsible parties** (pick **Mine**, one party, or **No owner**).
3. Click the policy. It opens on the **Content** tab.
4. To read an older version, pick it in **Read as it stood**, or open **History** and use **Compare versions**.
5. Open the **Requirements** tab to see which requirements it implements, evidences or references.
6. Click **Print** or **Export Word**.

To add a policy, click **New policy**, pick the **Family** and **Type**, type a **Title**, an **Owner** and how often it is reviewed, and click **Create draft**. A policy that has been published is retired, never deleted, so its history stays on record. Only a draft that was never published can be deleted.

## Comment on or change a policy

1. To point out a problem without editing, select a few words in a section on the **Content** tab, write under **What is wrong with this passage?** and click **Add note**. Follow it up on the **Notes** tab.
2. To change the policy, click **Edit** on a section, change the text and write the reason in **Why**. Click **Save**. The change is sent for approval, and the published version stays in force until it is approved.
3. Use **Add section** or **Remove section** as needed. Each save joins the same proposed change.

To show who to contact in a policy, write a paragraph that reads only `{{contacts}}` (every responsible party) or `{{contacts: CUI Data Owner; IT Manager}}` (those parties, in that order). The reader, the printed copy and the Word export show a table of each role, who holds it, and their phone, email and hours, taken from **Responsible parties** as they are today. A new holder or a new phone number then needs no policy change.

## Approve a policy change

1. Open **Policies** and the **Policy approvals** tab.
2. Under **Awaiting a decision**, click **Review and decide** on a card.
3. Read **Before (published)** and **After (proposed)** for each changed section.
4. Set the **Effective date** and click **Approve and publish**, or write a **Decision note** and click **Reject**.

Anyone with **Approve policy changes** can decide a change, including the person who proposed it. The published version records who submitted it, who approved it and when it took effect.

## Record a policy's review

1. Open the policy and click **Record review**.
2. Pick the **Outcome**: **Reaffirmed — no change needed** or **Revised — a new version was published**.
3. Add notes and click **Record review**.

## Find the gaps in the policy library

1. Open **Policies** and click **Coverage**. It lists the requirements of the chosen framework that no policy states yet.
2. Or open **Reports** and click **Policy coverage report** to print it.

## Keep evidence records and forms

1. Open **Evidence** and pick the system in the first drop-down.
2. **Records (what to collect)** lists each record: the report or export collected, who collects it, how often, and the objectives it answers. Pick **Complete for this assessment** or **Not complete yet** to see where you stand. **By system** lists every evidence source by where it comes from.
3. Filter by environment, by kind of evidence (signed forms and training, posted notices, external systems, Work Orders and recertification, policy reviews) or by responsible party.
4. Click **New record** (or **Add evidence source** in **By system**). Fill in **Report or export collected**, **System**, **Responsible party**, **How often**, **How it is proven**, **Kind of evidence**, **Link** and **How to get it**. Under **Sources it answers**, click **Add or change sources…** to pick the requirements and objectives it covers. Click **Create record**.
5. **How it is proven** is the usual way: **Verbal review and approval** (the default for new records), **Upload a file**, **Written statement**, **Interview**, **Observed or tested** or **Captured automatically**. Only a file needs an upload; the others are written down when they are recorded.
6. For **Captured automatically**, choose the connection: **Policy library** (then pick the policy and section, and the record shows **Tracked in Policies**: the approved version and its reviews are the evidence), a Work Orders request type, the access recertification or the CUI access register.
7. To change one source in the record, click its pencil in the form. Pick the **Policy section that asks for it**, and check **Required by**: the regulations from the requirement fill in themselves. Tick **Our choice** if only your own policy asks for this evidence, or tick anything else that also requires it.
8. To record a record, click **Affirm**, **Upload**, **Record** or **Confirm** on its row. The form opens over the list, so you keep your place. Tick the objectives it shows, set **Performed on**, add a note or file, tick the confirmation and click the button at the bottom. Each ticked objective is recorded **Met**, and one upload counts for every source in the record that shows the same objective.
9. For a verbal review, click **Affirm**. Review it with the responsible person (ask them, or look at the screen or the room), then fill in **Reviewed with** (optional) and **Reviewed on**, tick the **Objectives it shows**, tick **I reviewed this and approve: each ticked objective is met.** and click **Affirm met**. No file or write-up is needed; **Notes / comments** and **Add an attachment** are there if you want them. If it doesn't apply, click **Does not apply?**, say why and click **Mark not applicable**.
10. To prove it another way this time, change **How it is proven this time** (for example, a written statement that nothing happened this period). If it does not apply, set **Result** to **Not applicable (with a justification)** and say why.
11. For a captured record, read what was captured and click **Confirm**. If nothing was captured, click **Record** and record it by hand.
12. Click **Records report** (or **Generate report** in **By system**, with **Waiting on an answer** and **Objectives with no evidence linked**) for a printable copy.
13. On **Forms**, filter by environment and click a form to open its PDF. **New form** adds one; then upload its PDF and Word file.

## Draw a diagram

1. Open **Diagrams** and click **New diagram**.
2. Type a **Name**, an optional **Group**, and pick the **Kind**.
3. Under **Start from**, pick **Blank**, **Enclave boundary**, **Network topology** or **Swimlane workflow**, and click **Create**.
4. Drag shapes and icons from **Shapes**, assets from **Assets** or the **Scope list**, and draw connectors. Click **Save**.
5. If your workspace uses Microsoft 365, open **Data sources** to place its devices and people with their current name, model, user, job title or department. An administrator first connects Microsoft 365 under **System Settings**, **Integrations** and gives Regulatory Compliance its devices or people.
6. Use **History** and **Restore** for older revisions, **PNG** or **SVG** to export, or **File as evidence**.
7. Or ask the **Compliance Officer** to draw it for you, for example "Draw the enclave boundary with the file server, the firewall and the two engineering workstations inside it." It shows an outline first and saves only after you say yes. A drawing it replaces stays in **History**, so you can restore it.

## Read the POA&M and the SPRS score

1. Open **Reports**, click **POA&M report** and choose the system.
2. Read the SPRS panel: **Can it be filed as Conditional?** and **What to enter in SPRS**. You enter those values in SPRS yourself; the module does not file them.
3. Read the open items. Plans past their date are marked **PAST DUE**.
4. Click **Open in new window / Print** or **Download CSV**.

## Keep the System Security Plan

1. On a requirement, scroll to **Implementation narrative (System Security Plan)**, click **Edit** (or **Describe**), write a **Change note** and click **Save narrative**.
2. Open **Reports**, click **System Security Plan** and choose the system.
3. Click **Open in new window / Print** or **Export Word**.
4. When you are ready to affirm, click **File snapshot**. An approver then decides it under **Policy approvals**.

## Use the dashboard and stakeholder reports

1. Open **Reports**. **Compliance dashboard** shows each framework at a glance: validations overdue, open POA&M items, the SPRS score and the policy library.
2. Pick another report in the list, such as **Active Assessment Status Report**, **Forms and evidence schedule** or **Evidence records needed**.
3. Click **Open in new window / Print** to share it.
4. Under **Audit progress**, click **Take snapshot** or **Record a prior assessment** to keep a record of an assessment.

## Run the access recertification

1. Open **Reports**, click **Access recertification**, set the period dates and click **Start recertification**.
2. Each CUI owner opens **Access recertification** in the sidebar and clicks **Still needed** or **Withdraw** (with a reason) on each entry. **Undo** reverses a decision while the run is open.
3. Click **Export list (CSV)** and fill in the **Reconciliation** findings.
4. When every entry is decided, click **Complete recertification** and confirm. Each withdrawal opens a **Remove access** work order in Work Orders.

## Who can do what

Each action in the module needs a permission. A Workspace Admin gives permissions to roles; see [Users and roles: create and edit roles](article:88d4e232-d5b8-4909-b452-cfe96d3d550f). **Out of the box** shows the module's starting roles that have it.

| Permission | What it lets someone do | Out of the box |
|---|---|---|
| **View the compliance program** | See everything in the module: requirements, schedules, validations, evidence, regulations, policies, forms, diagrams and reports. | Admin, Operator, Viewer |
| **View assigned items** | See only the requirements, evidence sources, forms and policies assigned to their responsible parties. | Admin |
| **Record checks and upload evidence** | Record validations and upload evidence for any requirement, write System Security Plan narratives and propose policy changes. | Admin, Operator |
| **Record checks for assigned items** | Record validations and upload evidence only for the objectives assigned to their responsible parties. | Admin |
| **Comment on policies** | Leave and answer review notes on a policy without being able to change it. | Admin, Operator, Viewer |
| **Approve policy changes** | Approve and publish, or reject, a proposed change to a policy or a filed System Security Plan. **Give with care.** | Admin |
| **Manage standards and requirements** | Set up frameworks and systems, create and edit standards and requirements, manage responsible parties, add to the regulations register, file System Security Plan snapshots and run the admin repair check. **Give with care.** | Admin |
| **Manage all forms** | Add and edit any form, upload or replace its PDF and Word files, and link forms to policy sections and evidence. | Admin |
| **Manage assigned forms** | Add forms owned by their responsible parties, and edit or upload the files of the forms they own. | Admin |
| **Manage all evidence sources** | Add, edit and remove any evidence record or source, and choose how and on which form it is collected. | Admin |
| **Manage assigned evidence** | Add evidence sources for the objectives assigned to their responsible parties, and keep the ones they own current: where it is, how to get it and how often. | Admin |
| **Edit diagrams** | Create, edit and restore network, boundary, data flow and workflow diagrams, and place Microsoft 365 devices and people on them. Seeing diagrams needs only View the compliance program. | Admin, Operator |
| **Review access recertifications** | Keep or withdraw entries in an open access recertification, and nothing else in the module. **Give with care.** | Admin |
| **Delete compliance records** | Delete standards, requirements, recorded checks, assessment snapshots, diagrams and responsible parties. **Give with care.** | Admin |

## Ask its agent

Regulatory Compliance has an assistant, the **Compliance Officer**. It answers from your records and asks before it records anything. See [Agent chat](article:073c6465-d85c-4364-8768-acf42a3a6a48). For example:

- "What compliance items are overdue in the Internal Security Review?"
- "When is SAMPLE-6, the incident response plan, due?"
- "Which requirements have no policy covering them?"
- "Draw a network diagram of our enclave from the assessment scope."

## Good to know

- Scores, the POA&M and the SPRS score are worked out from the validations you record. To change them, record a new validation; nothing is edited by hand.
- A score counts only for the current window. Last year's **Met** is history, and the letter is due again this year.
- A **Not met** opens a POA&M item; a later **Met** on the same objective closes it.
- A policy change never takes effect until it is approved. Earlier versions are kept and can be compared.
- SOC 2, ISO/IEC 27001 and The Joint Commission show as coming soon. Today only CMMC and custom standards can be set up.
- The module tells you what to enter in SPRS, but you file it in SPRS yourself.
- HR onboarding documents and Microsoft Graph show as **Not connected yet** under **Captured automatically**. Record those by hand for now.
- People with only the assigned-items permissions see **Compliance**, **Policies**, **Evidence**, **Regulations** and **Forms**, not **Diagrams**, **Responsible parties** or **Reports**.
- Requirement status, validations, evidence sources and files, policies with their changes and reviews, the assessment scope, assessments and access recertification entries are available for reports and dashboards. See [Dashboard](article:1d8a33a4-3a13-4874-b8e5-5ef9da22df95).

## More help

Regulatory Compliance has no Help page of its own. It comes with nine runbooks: **Getting started with Regulatory Compliance**, **Record a validation of an assessment objective**, **Record reviewed policy objectives together**, **Find, read and comment on a policy**, **Change a policy and get the change approved**, **Read the evidence page, the checklist and the evidence report**, **Work the POA&M and file the SPRS score**, **Update, print and file the System Security Plan** and **Run the periodic access recertification**. See [Find and follow a runbook](article:4b62ad1f-577a-4998-8bce-f00226376522).


Source: https://datavisions.ai/docs/module-guides/regulatory-compliance
