For the CISO
Know your compliance status on any day
The board wants assurance, the regulator wants timelines and your team wants one place to work. xmodo answers all three from the current status of your controls.
Questions you can answer at any time
- What is our compliance status today for each framework, and what changed it this week?
- Which controls are failing, who owns them, and when was evidence for them last provided?
- How long did our last reportable incident take from detection to notification?
- How much of the new regulation do we already meet through existing controls?
Each answer links to the control, evidence, owner and date behind it.
Today
The situation today
The board asks whether you are compliant. The regulator asks why an incident took nine hours to report. Your team asks which of four frameworks this quarter's work should serve. Three spreadsheets give three different answers.
Assurance goes out of date
A compliance report is accurate on the day it is written and becomes less accurate afterwards. Often nobody notices until an examiner finds an attestation that expired in the spring.
Reporting deadlines are missed
A statutory reporting window starts when an incident is detected, before it is escalated. When the timeline sits in an email thread, delays come to light in the post-incident review.
The same work is done several times
The same access-control requirement appears in four frameworks. Without a shared control, your team implements it once and provides evidence for it four times every year.
With xmodo
What changes
One current status
Controls implemented, risk score and evidence coverage are recalculated from the current status of your controls. When a figure changes, you can show why.
Reporting deadlines built in
Each incident record shows the time of detection and notification, and how long remains before the jurisdiction's reporting deadline.
Trace any figure to its source
Each incident links to the control gap, the audit finding and the corrective action that closed it, so you can answer questions straight away.
For the board: the compliance trend week by week, with every figure traceable to its source.
Your first week
Your first week with xmodo
Day 1
Adopt your two most demanding frameworks. The mapping between frameworks shows what your existing programme already meets before anyone plans work.
Day 3
Load a sample of current evidence. Expiry dates are attached, and the first renewal tasks appear for real owners.
Day 5
Trace one incident from start to finish with your own team: the gap, the finding, the corrective action, closure and the evidence.
What you own
Reports you can produce
Board compliance report, generated from the current status of your controls
Incident timeline for the regulator, with detection and notification timestamps
Framework coverage summary with the list of real gaps and named owners
Exception register with expiry dates and approval history
Modules
The modules you would use
Compliance
Frameworks, gap analysis and current compliance status.
OpenIncident
Response deadlines and regulatory reporting times.
OpenAudit & CAPA
Findings with owners, due dates and closure.
OpenGet a demo on the framework that concerns you most.
Colleagues
Who you work with in xmodo
Frequently asked questions
Can I present directly from the dashboard?
Yes. The dashboard is calculated from the current status of your controls. Every figure traces to its source: the control, the evidence, the owner and the date.
How does xmodo handle multi-entity groups?
Each entity has its own registers, frameworks and compliance status within your organisation's account. These roll up to a group view, so each entity's obligations stay separate while the board sees the whole group.