Control monitoring
Keep a running health reading on every control in your frameworks, so a control that is weakening shows up here before an auditor or an incident finds it.
A control is a safeguard against a risk — requiring multi-factor authentication, for example. A control you never check is only a statement of intent. This page keeps a monitor (a scheduled automatic check) against each control in the compliance frameworks you have enabled, and shows a health status for each. A background job re-checks the monitors that fall due every thirty minutes; alongside it you record your own test results by hand, which build a dated history.
Control monitoring sits in every licence tier's default feature set; where a
licence does not carry it, the page reads “Control monitoring is not
available on your current plan. Upgrade to enable continuous control
monitoring.” instead of the table. The module has to be provisioned for your
tenant as well — without that, the sidebar entry is hidden and opening
/control-monitoring directly sends you back to the Dashboard.
Who uses it
Reading is open to every role. Changing anything needs ccm:update,
held only by Manager and Admin. Buttons you cannot use are hidden rather than
refused — the one exception is the initialise action below.
-
Viewer and
Contributor filter the
list, open any monitor and run the AI triage. Neither sees
Record Test ResultorDisable Monitor. - Manager also records test results, switches a monitor off and back on, and runs the initialisation.
-
Admin does all of that, and
alone reaches
/settings/control-monitoringto add, edit or delete monitors.
What's on this screen
The page opens on the /control-monitoring list. On the left, the
sidebar groups every module — Governance, Risks, Compliance, Audit, Documents
and the rest — with control monitoring inside Compliance,
collapsed until you open it. Along the top run your organisation's name, global
search, the language picker (EN), the dark-mode switch, the Help
“?”, the User Guide book icon, your notifications, your initials and name, and
Sign out. A round AI assistant button floats in the bottom-right
corner.
The header reads Control Monitoring over its one-line description,
with a single action — Monitor Triage (AI) — at the far right.
Below it sit three filter dropdowns, each showing only its current value and no
label: All Statuses, All states and
All reviews. Left to right they filter by Status,
Enabled and Review. Then the table, twenty
rows to a page: Ref, Control (long titles are
cut short with an ellipsis), Type, Status,
Last Checked and Enabled. Dates follow the
language you have chosen. There are no per-row buttons and no tick-boxes —
selecting a row opens that monitor over the list. Below the table sit your saved
AI briefings and the action items raised from them.
The captured screen shows monitors from more than one framework side by side —
ISO 27001 Annex A references such as A.5.15, NIS2 references such
as NIS2-RM-1 and a DORA reference — with a mix of monitor types.
Most rows read green Healthy; a few read amber
Warning, one red Critical and one grey
Unknown, and every monitor is enabled.
-
In the sidebar, open the Compliance group and select
Control Monitoring. The group expands and the list loads, with the entry highlighted while you are on the page. - The book icon in the top bar opens this guide at the chapter matching the page you are on. The “?” beside it opens a separate help panel that slides in with short topics for the page and a search.
- Your name at the top right shows the account you are signed in as; selecting it, or your initials, opens your profile. Your role decides whether the write buttons appear inside a monitor — this capture is a Contributor, so they do not.
-
Monitor Triage (AI)sits at the right of the header. Selecting it opens the triage panel described below; it reads your monitors and changes nothing.
Setting up the monitors the first time
-
Open
/control-monitoring. With no monitors yet, the table is replaced byNo monitors configured, a line explaining that initialising creates monitors for all your framework controls, and anInitialize Monitorsbutton. -
Select
Initialize Monitors. Aegis creates a compliance-score monitor for every current control of an enabled framework that lacks one, refreshes the table, and confirms with “Control monitors initialized.” Running it again only fills gaps. Controls retired from a framework's catalogue get no new monitor. -
The new rows read grey
UnknownwithNeverunder Last Checked until the job reaches them — once a day for these monitors.
This action is not hidden from a Viewer or Contributor, but the request
behind it needs
ccm:update and is refused. If you see “Could not initialize
control monitors.”, ask a Manager or Admin.
Narrowing the list
-
Open the first dropdown,
All Statuses, and pick one of the five statuses. The table reloads showing only that status;All Statusesrestores the rest. -
Open the second,
All states, and chooseEnabledorDisabledto separate the monitors you are watching from those switched off. -
Open the third,
All reviews, and chooseOverdue review— its only other option. Only monitors past their next review date stay on screen. The filters combine.
Opening a monitor
-
Select any row. The detail opens over the list, titled
Monitor: <reference>, status badge at the top. For a Manager or Admin,Disable MonitorandRecord Test Resultsit beside it. -
A monitor that Aegis manages for you carries a blue note beside the badge
instead of
Disable Monitor: “Managed by the FedRAMP ConMon cadence” or “Managed by the Entra ID connector”. Its schedule and on/off state belong to that source; you can still record a test result against it. - Framework Control gives the control's reference and title; Monitor Configuration the type, the check interval, the last and next check, whether the monitor is enabled, and its status. Times show in your own time zone.
- Four sections appear only when there is something to show: Thresholds where the monitor carries its own warning and critical day counts, Linked security processes on a Jira process adherence monitor, Recent Alerts once alerts have been raised, and Last Check Details once a check has run — the readings behind the status, as labelled rows.
-
Review Cycle gives the interval in days, the last tested
date and the next review, with a red
Overdue Reviewbadge once that date has passed. Linked Risks names the risks this control mitigates with their status, read-only here; Test Results holds the dated history, newest first; and Metadata closes the panel with the created and last-updated dates.
Recording a test result
A test result is your own check of a control, written down. It needs Manager or Admin.
-
Open the monitor and select
Record Test Result. A small form opens with three fields. -
Choose the Result:
Pass,FailorPartial. It opens onPass. - Write your Notes — what you tested and what you found. Optional, up to 5,000 characters, and what makes the entry useful to an auditor later.
-
Optionally pick a record under Linked Evidence. It opens on
No evidenceand lists your newest 100 evidence records by name; if you cannot read evidence, the picker stays greyed out. -
Select
Save Test Result. “Test result recorded” confirms it and the entry appears at the top of Test Results with its badge, timestamp and the name of any linked evidence. The review cycle is recalculated from it; the status badge is not.
It stamps the result as you save and takes no attachments. Upload your proof under Evidence first, then link it here — or name it in your notes if it is older than the newest 100 records the picker offers.
Switching a monitor off and back on
-
Open the monitor and select
Disable Monitor. It stops being checked and stops raising alerts, the list showsNounder Enabled, and its history survives. -
To resume, select
Enable Monitor. Checking restarts at the next scheduled run rather than immediately.
A managed monitor (FedRAMP ConMon or Entra ID) has no on/off button; its source switches it.
How a status is decided
Each monitor has a type, and the job reads the source that
matches it: the control's own status and maturity (compliance score), the age of the linked evidence (evidence freshness), or whether
linked policies, risk assessments or vendor assessments are overdue. Readings
are counted in days against two thresholds, 30 and 7 by default: a due date 30
days out reads Warning and 7 days out Critical, while
evidence reads Warning past 30 days old and
Critical past 37. A control with no evidence linked reads
Warning. When a check moves a monitor to Warning or
Critical, an alert is recorded and every Admin and Manager is
notified; for a review-type monitor (periodic review or FedRAMP ConMon) the
control's owner group is notified instead. A move to Unknown raises
no alert.
Other types read their own source: a Jira process adherence monitor
grades the security processes linked to the control on their on-time rate, open
SLA breaches, procedure step deviations and how recently a Jira sync confirmed
them; the Entra ID monitors grade privileged access and leavers whose accounts
are still enabled after each directory sync.
| Status | What it means |
|---|---|
Healthy |
The last check found the control inside its thresholds. |
Warning |
Degrading — stale evidence, a review falling due, a control not yet started. |
Critical |
The control is non-compliant, or past its critical threshold. |
Unknown |
Never checked, or nothing to grade yet. Expect this straight after initialisation. |
Disabled |
Switched off by a person. Not checked, raises no alerts. |
Read the column as a measure of how much assessed, current data stands behind each control, not a verdict on your organisation. A green row says the last check found nothing out of bounds; it does not say the control is finished.
The AI assist
Monitor Triage (AI) answers one question: of everything that is not
healthy, what should you deal with first? Aegis ranks the monitors needing
attention — Critical, Warning and
Unknown — by status, control importance, unresolved alerts and
overdue checks. That ranking is Aegis's own and reproducible; the AI narrates it
with a next step per entry, and cannot reorder it or invent monitors.
-
Select
Monitor Triage (AI). A panel opens headedAI Control-Monitoring Triage, explaining what triage covers and noting that it changes nothing. -
Select
Run Monitor Triage. The progress line moves through scanning, finding failing monitors, ranking and drafting, and the plan streams in as it is written. -
Decide what to do with the result:
Copy,Export DOCX,Export PDF,Save as recordto keep it below the table, orRun again. - The panel also offers the at-risk monitors as a tick-list of ready-made action items, each titled with its real control reference. They arrive already ticked, so clear the ones you do not want before creating them; the rest appear on the Action items workbench.
Triage covers the fifteen highest-ranked monitors, so on a large tenant read it as the top of the queue rather than the queue. Each run carries a confidence indicator and the records it drew on. It is a reading list, not a decision — a person reviews it and acts — and each run costs one AI action against your allowance.
Periodic reviews
A periodic review is a recurring check a
person carries out by hand and records with evidence — a monthly log review, a
quarterly review of break-glass use, a quarterly access-rights review. The
Periodic review monitor type tracks one per control. Its status
follows the monitor's own next review date: Warning once the date
is a quarter of the interval away (never less than one day or more than thirty),
Critical once it has passed. When a review is overdue, the
control's owner group (or, without one, every Admin and Manager) receives one
notification per review cycle, “Review of control … is overdue”, with a link
back to this page. Recording the review — a test result, ideally with its
evidence linked — moves the next date on by the interval and re-arms the
reminder.
You can add a periodic review to any control from
/settings/control-monitoring. For Dutch healthcare there is a
shortcut: Create recommended reviews on the
NEN 7510 hub adds four at once — a monthly log
review on NEN 7510 8.15 and NEN 7513 5.2, and quarterly reviews on NEN 7510 8.2
(break-glass) and 5.18 (access rights). Running it again creates only what is
missing. The hub's Periodic reviews
tile then counts how many are due and overdue.
Tips and limits
- Recording a test result does not move the status badge. The two are deliberately separate: the badge is what the check read from your data, the result is what a person confirmed by hand.
-
The list has no create form, no search box, no CSV export and no bulk
selection. An Admin adds, edits or deletes individual monitors at
/settings/control-monitoring, choosing from seven types —Evidence Freshness,Policy Review Due,Risk Assessment Due,Compliance Score Threshold,Vendor Review Due,Jira process adherenceandPeriodic review. For a new control, add it to its framework first, then initialise again. -
Three further types can appear in the list but cannot be created by hand:
FedRAMP ConMon review,Entra ID privileged accessandEntra ID leaver access. Aegis creates and maintains them from the FedRAMP catalogue and from the Entra ID connector. - Disabling is reversible; deleting a monitor is not. A status can lag the data by up to the monitor's check interval — a day for the monitors the initialise action creates — because there is no “check now” button here.
Where this connects
The controls monitored here come from your Compliance frameworks; their proof lives in Evidence. The readings feed Audit readiness; a failing control is a live input to Risks, mapped in Control mapping. Jira process adherence monitors grade the Security processes linked to a control, fed by the Jira connector. Triage work lands in Action items; roles are in Roles overview.