Skip to content

Controls ​

Controls are the "how" of compliance: the measures that you apply to satisfy Requirements. One Control can map to Requirements of more than one framework, and it keeps the record that an audit uses.

What this is ​

A Control is a unit of work that you can use for more than one Requirement. One good Control can satisfy Requirements of different frameworks, and you do the work only one time.

A Control has three parts:

  • narrative: the report that tells what you do and why it satisfies the obligation
  • proof: the Evidence and the Policies that are attached to the Control
  • decision history: the comments and the logs in Comments and Logs

For the full operating model, see Governance Operating Model.

Where in Modulos ​

  • AI System → Controls to see the Controls of an AI System and open one. Control codes sort in number sequence (MCF-2 before MCF-10). To filter the Controls:
    • The sidebar filters by status and by Assigned to me.
    • The Filter button has these filters: Framework (one framework), Lifecycle Stage (one lifecycle stage), Tags (one or more tags), and AI Assessment (Assessed or Not assessed). AI Assessment shows when the Control Assessment Agent is available to your organization.
    • Lifecycle Stage marks the current lifecycle stage of the AI System with Current. Its last value, No stage (continuous obligations), shows the Controls that have no AI System Lifecycle tag. Unless you also filter by status, these include Out of Scope and Archived Controls.
    • When the AI System has a lifecycle stage, the Controls page opens with the Lifecycle Stage filter set to the current lifecycle stage. A link that has filters in its address opens with its own filters. To see the Controls of all lifecycle stages, remove the Lifecycle Stage filter.
    • The active filters show as chips above the Controls.
    • The address of the page keeps the filters and the search. A copied link opens the same filtered Controls. When you close a Control, the same filtered Controls show again.
  • Open a Control to see its tabs: Control, Report, Assessment, and Comments and Logs. The Assessment tab shows the result of the Control Assessment Agent when this agent is available to your organization.

Who can do what ​

Permissions

  • All members of an AI System can see its Controls, the Evidence, and the history.
  • AI System Owners and Editors can edit Controls and attach Evidence.
  • The Control Owner does the work of the Control. The Control Owner must be an AI System Owner or an Editor. The owner of a mapped Requirement selects the Control Owner.
  • Only the Control Owner or the owner of a mapped Requirement can change the status of a Control, whatever their organization role. The table below shows who sees the Status selector and which changes Modulos saves.
  • Viewers can see Controls, Evidence, and the history, and they can add comments. They cannot change Controls or Evidence.
WhoStatus fieldStatus change
Control OwnerSelectorSaved
Owner of a mapped RequirementSelectorSaved
Other AI System Owners and EditorsSelectorRejected
Organization Admins, Risk Managers, and Policy Managers (access to all AI Systems)SelectorRejected, unless the user also is the Control Owner or the owner of a mapped Requirement. This needs the AI System role Owner or Editor.
ViewersTextNot possible

Modulos rejects a change from other users with the message "Only Control Owner or Requirement Owner can change the Status of a Control." A mapped Requirement that is Fulfilled blocks the change for everyone. For this lock, see Locking and why it matters.

A Control with the Control tab open: the Overview and Evidence sections on the left, and Status, Owner, Mapped Frameworks, and Mapped Requirement(s) on the right.

A Control holds the guidance, the Evidence, and the Policies, and shows its status, its Owner, and the Requirements that it maps to.

  1. Control Holds the question, the user guidance, and the Evidence.
  2. Evidence Attach the Evidence that shows how the Control is done.
  3. Status The Control Owner or the owner of a mapped Requirement changes it.
  4. Mapped Requirement(s) The Requirements that this Control helps to satisfy.

How it works ​

Control anatomy: sections and Evidence ​

Each Control has the same parts, on its tabs and in the right panel:

  • Control tab The guidance and the proof
    • Overview The question and the description of the Control
    • User Guidance Instructions for the Control, if the Control has them
    • Evidence The Evidence files, and the published Policies in Associated Policies
  • Other tabs The narrative, the AI assessment, and the history
    • Report
    • Assessment
    • Comments and Logs
  • Right panel The status and the links
    • Status and Owner
    • Mapped Frameworks and Mapped Requirement(s)
    • Assessment, TAGS, and Associated Runtime Inspections

The Assessment tab and the Assessment item in the right panel show only when the Control Assessment Agent is available to your organization.

You write the narrative on the Report tab and select Submit. Each Control has one Evidence section for all its Evidence files. One Evidence item can be attached to more than one Control. For the Evidence rules, see Evidence.

Status changes ​

A Control is Not Executed, Executed, Out of Scope, or Archived. The Control Owner or the owner of a mapped Requirement sets the status directly in the Status field, and Modulos logs each change. There is no reviewer approval. A comment is necessary only when an Executed Control goes back to Not Executed while a mapped Requirement is ready for review. For who can change the status, see Who can do what. For all the status rules, see Reviews & Statuses.

Locking and why it matters ​

While a Control is Executed, Out of Scope, or Archived, Modulos locks it:

  • you cannot edit the report, attach Evidence, or add tags
  • the Owner field is locked, but the owner of a mapped Requirement can change the Control Owner with Assign To in Mapped Controls
  • while the Control is Executed, you cannot remove its Evidence, and its Evidence is locked too. An Out of Scope or Archived Control does not lock its Evidence. See Evidence.

You can change the status again, but not while a mapped Requirement is Fulfilled. Modulos logs each change, and the lock keeps the record of the audit correct.

A Control connects these items:

  • Requirements map to Controls. A Requirement is ready for review when all its mapped Controls have a final status.
  • Evidence and Policies attach to the Control as proof. When a user archives a linked Policy, Modulos sets an Executed Control to Not Executed and removes the Policy from a Not Executed Control. See Lifecycle & Approvals.
  • Metric Tests and Agent Tests show in Associated Runtime Inspections. You can add a test with Associate to a Test, or remove one, only while the Control is Not Executed. When a mapped Metric Test fails or has an error, or a mapped Agent Test fails, Modulos sets an Executed Control to Not Executed. See Results & Remediation.

How to use it ​

  1. Select a Control Owner The owner of a mapped Requirement selects who does the work: an AI System Owner or Editor.
  2. Write the report Tell what you do and how it satisfies the obligation.
  3. Attach Evidence Attach the files that show that the Control is done.
  4. Set the status The Control Owner sets the status to Executed.

Important considerations ​

  • Start with the Controls that map to many Requirements. One Control that satisfies Requirements of more than one framework gives the most value, and the work grows less as you add frameworks.
  • Set Executed only when the Control is done and has Evidence for this AI System.
  • If you must reopen an Executed Control, tell why in a comment. Reopened work is usual in governance, and the comment keeps the cause on the record.