Regulatory Watch
EterShield automatically monitors public EU regulatory sources and uses AI to propose relevant updates to your compliance calendar, without publishing anything without human review.
How it works
- A scheduled job runs weekly and fetches RSS/Atom feeds from public regulatory sources:
- EDPB (European Data Protection Board)
- European Commission: Digital Policy (Digital Strategy)
- European Commission: Press (news filtered for cybersecurity)
- Each item is filtered for relevance (discarding non-regulatory noise) and then analysed by AI (Claude), which extracts: title, summary, affected framework(s), country(ies), type and estimated impact.
- The draft is saved as unpublished: it never appears in the calendar automatically.
Coverage note: CNCS and CNPD do not provide accessible RSS feeds (they are behind a WAF), so national coverage is indirect, through the EU feeds above.
Review queue
In a dispute, Reanalyse asks the AI for a new suggestion based on the current values of the disputed record (and not those that existed when the dispute was opened), using your comment as an instruction. It never changes the record: the proposal only applies if you accept it.
At Review Queue, in the "Regulatory updates (AI)" section, you will find the list of pending drafts with:
- Title, type, impact level and source
- Associated framework(s) and country(ies)
- Link to the original source ("source" button)
- AI-generated summary
For each draft, an administrator can:
- Publish: the item becomes
published: trueand automatically appears in the Calendar ("Regulatory deadlines" section) - Reject: the draft is discarded
Oversight note: No regulatory update reaches the calendar without explicit human approval.
Impact on frameworks
Each regulatory update now shows a badge with the concrete impact on the tenant: number of active frameworks affected and total controls covered. Clicking "See impact on frameworks" expands a panel with the detailed list: framework code, name, number of controls and whether it is active in the tenant or not.
The match between the free-text name of the update (e.g. "EU AI Act", "Cyber Resilience Act", "ISO 42001") and the framework code in the catalogue (e.g. EU_AI_ACT, CRA, ISO42001) is made by alphanumeric normalisation, by code and by name, with known aliases (e.g. "AI Act", "GDPR", "AMLD"). When there is no match for a code mentioned in the update, the panel states this explicitly rather than hiding it.