Regulatory changes

A feed of incoming regulatory developments, scored for relevance, with a dated record that a named person read each one — and AI actions that help you decide what to act on first.

A directive amendment or a supervisory authority decision can undo a control mapping that took months to build; this module gives that watching work a home. Aegis ingests developments from external sources — the GDPRhub (a public database of European data-protection decisions), the news feeds of European and national authorities such as the EDPB, EBA, ESMA, EIOPA and Belgium's CCB (Centre for Cybersecurity Belgium), and other registered feeds — scores each for relevance to your organisation's profile, and lists them for review. You mark an item reviewed, leaving a dated record that you looked, or dismiss it as not applicable to your organisation.

You use that history to keep on top of the regulatory calendar; auditors use it to confirm you monitor change systematically — something ISO 27001, NIS2 (a European cybersecurity law), DORA (the EU operational-resilience regulation) and the EU AI Act all expect.

A licensed module

Regulatory Changes is gated by the REGULATORY_INTELLIGENCE module and feature. Without the feature, the page shows a short "not available on your current plan" notice instead of the feed; without the module, the sidebar link is hidden altogether.

Who uses it

Every role that holds REGULATORY_READ can open the page; anyone without it is sent to the unauthorised page. What you can do once there depends on two more permissions: REGULATORY_WRITE for changing an item's state, and the right to run AI actions (which spend AI credits).

When an administrator has switched AI off for the whole tenant, the Relevance Triage (AI) and Suggested actions buttons are hidden for every role. Analyze impact stays visible to Managers and Admins, but Aegis refuses the request while AI is off. The review and dismiss controls are unaffected.

What's on this screen

The header reads Regulatory Changes over the line "Track incoming regulatory updates and assess their impact on your compliance posture", with one button opposite: Relevance Triage (AI). There is no "add change" button — items arrive from the ingested sources.

Under the header runs a filter bar of four controls: a search box (placeholder "Search regulatory changes…"), a Search button, an All Sources dropdown built from the sources your tenant has actually ingested rather than a fixed list, and a view dropdown set to Active that you switch to Dismissed to see items set aside. Once any filter is set, a Clear filters button appears at the end of the bar. The body is one table, newest publication first (items without a date sort last), with five columns:

Column What it shows
Title The headline from the source — on the captured screen a mix of authority announcements, such as an EBA consultation or an EDPB guideline, and national decision references such as "DSB (Austria) - DSB-D124.2437/25". Long titles truncate.
Source The feed it came from. The captured screen shows items from, among others, EBA, EDPB, CCB, ESMA, GDPRhub DPA Decisions, CERT-EU Security Advisories and NIST Cybersecurity.
Relevance A stored score from 0 to 100%, shown as a coloured badge: green below 40%, amber from 40% to 69%, red at 70% and above.
Published The publication date from the source, or a dash when the source gave none.
Status Pending Review in grey until someone reviews the item, then Reviewed in green. In the dismissed view, an amber Dismissed badge instead.

Selecting a row opens that item in a detail panel. The feed pages twenty rows at a time; below the pager sit two panels that stay empty until you use the AI actions, Saved AI insights and Action items. A tenant that has ingested nothing sees the table's empty state instead of rows. To get your bearings:

  1. Find the module in the left sidebar: selecting the Compliance group expands it and lists Regulatory Changes among its links.
  2. Note the Relevance Triage (AI) button opposite the page title. It works on the whole open queue, not on one row.
  3. Type into the search box to narrow the feed. The table reloads a moment after you stop typing; Search or the Enter key reloads it at once.
  4. Select the ? in the top bar to open in-app help over the page.
  5. Your name at the top right opens your profile page, where you can check your role — worth a glance, because the write and AI actions appear only for some roles.
The regulatory changes feed, seen as a Contributor — /regulatory-changes.
The regulatory changes feed, seen as a Contributor — /regulatory-changes.

Narrow the feed and pick what to read

The feed is ordered by publication date, not by relevance, and several sources land in the same queue — so narrow before reading.

  1. Type a regulation name, authority or keyword into the search box. The table reloads with items whose title or summary matches.
  2. Open the All Sources dropdown and pick one issuing body. A source you have never received items from does not appear in the list.
  3. Read down the Relevance column and start with the red badges — on the captured screen, eight of the thirteen visible rows score 70% or more, against one green row at 34%. The score is a stored first-pass estimate, not a judgement you have to accept.
  4. Switch the view dropdown to Dismissed to see what a colleague set aside, and back to Active for the review queue. Clear filters resets all three at once.

Read and review a change

Reviewing records that a person read the item, and on what date — which is what an auditor asks for, more than the headline itself.

  1. Select a row. A detail panel opens over the page, headed with the change's own title (or Regulatory Change while it loads), with a relevance badge such as 95% — High Relevance and the action buttons your role allows beside it.
  2. Read the Details block — source, identifier, publication date and relevance score — then the Summary, the item's text with the source site's formatting stripped out. Next to the score, a small badge says where it came from: Heuristic score, AI score or Manual override, with the date it was set.
  3. Where the item carries one, select View original document under Source Link; the issuing body's page opens in a new tab.
  4. With REGULATORY_WRITE, select Mark as Reviewed. A toast confirms "Marked as reviewed", a green Reviewed badge replaces the button, the row behind updates, and a Review section records who reviewed it and when.

Further down, the panel shows Impact Analysis, any Categories the item carries, a Metadata block with the created and last-updated dates, and the AI insights and action items saved against this change.

There is no un-review button

Marking an item reviewed stamps it with your name and the date, and the panel offers no way to undo that. Dismissal, by contrast, is reversible.

Dismiss what does not apply

Not every ingested decision concerns your organisation. Dismissing one takes it out of the active queue without deleting it, and records who did.

  1. Open the item and select Dismiss. A toast reads "Change dismissed" and the item leaves the Active view.
  2. The panel now shows a Dismissed section with the date and the person. There is no reason field on this screen — a Reason line appears only where one was recorded through the API.
  3. To reverse it, set the view dropdown to Dismissed, open the item and select Restore to queue. A toast reads "Change restored to the review queue".

Open a change from the intelligence feed

The Regulatory alerts feed links straight into this page. Selecting Assess change on an item there opens Regulatory Changes with that item's detail panel already open. Closing the panel returns you to the feed and removes the item from the address, so a page refresh does not open it again.

The AI assist

Three things here are AI-assisted. All draft; a person reads, decides and records. None marks an item reviewed, dismisses anything, or files work on your behalf.

The first time you start an AI action, Aegis may ask you to acknowledge an AI transparency notice; once you accept, the action you selected runs. The two streamed actions then run the same way:

  1. Select Relevance Triage (AI) in the page header, or Suggested actions in an open change. A dialog opens on a short explanation of what the action reads and what it will not do.
  2. Select Run Relevance Triage or Suggest Actions. Progress lines name each stage while the answer streams in.
  3. When it finishes, take the text away with Copy, Export DOCX or Export PDF, or select Run again.
  4. Save as record keeps it in Saved AI insights — on the change itself for Suggested actions, at the foot of the feed page for the triage. Create action item files it as work, shown in the Action items panel and in Action items.
The AI drafts; you decide

Treat a relevance score or a named framework as a prompt to look, not as a finding — check what the model names against your own control set first. Aegis assists; the organisation decides what a change means and what to do about it.

Tips and limits

Where this connects

Standing alerts for particular regulations, and the intelligence feed that links here, live in Regulatory alerts. The Dashboard can carry a regulatory changes card that opens this page. A change usually points at requirements in Compliance frameworks, GDPR, DORA or the EU AI Act. Track the work it creates as a risk or an action item, and file the source document in Evidence; for a worked example, see the regulation scenario.