Docs

Appearance

Governance ​

This page covers common problems with Requirements, Controls, risk quantification, Policies, and AI System registration. Each entry links to the page with the full procedure.

A Requirement has no Mark as Fulfilled button ​

Symptoms

  • The Requirement page does not show the banner "Requirement is ready to be reviewed. If all related controls are correctly executed mark this requirement as Fulfilled." with the button Mark as Fulfilled.
  • The button shows, but Modulos refuses the change with "Only Requirement Owner can change the status of Requirement".

Likely causes

  • The Requirement is not ready for review. At least one mapped Control has no final status. The final statuses are Executed, Out of Scope, and Archived.
  • The Requirement status is not Not Fulfilled. The banner shows only while the status is Not Fulfilled.
  • You are not the Requirement Owner. Only the Requirement Owner changes the status.

How to fix

  • Open the mapped Controls of the Requirement. Set each Control to a final status, or ask its Control Owner to do so.
  • If the status is Fulfilled and you must reopen the work, ask the Requirement Owner to set the Requirement to Not Fulfilled.
  • Ask the Requirement Owner to mark the Requirement.

Related: Requirements

A Control status does not change ​

Symptoms

  • Modulos refuses a status change with one of these messages:
    • "Cannot update controls of the fulfilled requirement" and the name of the Requirement
    • "Only Control Owner or Requirement Owner can change the Status of a Control."
    • "This control(s) belongs to a requirement that is ready for review. You must provide a reason for changing the status from 'Executed' to 'Not Executed'."

Likely causes

  • A mapped Requirement is Fulfilled. Modulos does not change the Controls of a Fulfilled Requirement.
  • You are neither the Control Owner nor the Requirement Owner of a mapped Requirement.
  • The Control is Executed, a mapped Requirement is ready for review, and you change the status to Not Executed without a reason. Modulos opens the dialog for the reason only when that Requirement is Not Fulfilled. For a ready Requirement with a different status, no dialog opens and Modulos rejects the change.

How to fix

  • Ask the Requirement Owner to set the Requirement to Not Fulfilled. Then change the Control status.
  • Ask the Control Owner or a Requirement Owner of a mapped Requirement to make the change.
  • To set Not Executed on an Executed Control under a Not Fulfilled Requirement that is ready for review, make the change on the page of the Control and type why in the dialog.

Related: Who can do what, Reviews & Statuses

A Risk Agent run is Unquantified ​

Symptoms

  • A threat shows the status Unquantified, and its value is zero.

Likely cause

  • The Risk Agent found too little data about the AI System and your organization to ground an estimate. It stops the run and does not give a number. This is not an error. A run with an error shows Failed.

How to fix

  • Add context for the agent: Evidence, Controls, a fuller threat description, or connected Sources.
  • Open the threat and select Recalculate. Only AI System Owners and users with access to all AI Systems see this button.

Related: Why did my Risk Agent run come back unquantified?, Risk Agent

A Policy cannot be published ​

Symptoms

  • The Policy version has no Publish button.
  • Ask for Approval is disabled.

Likely causes

  • The version is not Approved. Publish shows only on an Approved version.
  • You are not the owner of the Policy. Only the owner asks for approval and publishes.
  • The Policy is archived.
  • The content of the draft still has placeholders. Ask for Approval stays disabled until you replace them.

How to fix

  • Replace all placeholders, save, and select Ask for Approval. Another Policy Manager, or the owner, then selects Approve.
  • Ask the owner of the Policy to publish the version, or to unarchive the Policy first.
  • If Publish shows, select it, select a Renewal Period, and select Publish again.

Related: Policy lifecycle

An AI System stays in Pending ​

Symptoms

  • The registration status of the AI System is Pending and does not change.

Likely causes

  • Nobody with the right has decided yet. Only an Organization Admin or an Organization Registration Manager approves or rejects a Pending AI System. Modulos sends no notification to these users when an AI System becomes Pending.
  • The AI System was rejected. The status is then Rejected, not Pending. The Overview shows the reason as a comment.

How to fix

  • Ask an Organization Admin or an Organization Registration Manager to open the Overview of the AI System and select Approve or Reject.
  • After a rejection, read the reason, correct the AI System, and select Submit for review.

Related: Create an AI System