The ways logs, approvals, incident reports, and records get altered or faked, in plain language, and what DOR does about each one.
The clocks that start when something goes wrong, and the facts you report against them.
CMP-R.1
Reporting deadlines start when an organization knows, and attackers work to keep it from knowing.
DOR records what systems received and changed, so problems surface as they happen.
CMP-R.2
A changed clock or edited log can scramble the sequence regulators ask for.
DOR keeps the true order of events even if a clock is changed.
CMP-R.3
Records and approvals can be created later and dated earlier.
DOR locks in the order things happened.
CMP-R.4
Attackers pose as employees, executives, and help desks to get access.
DOR confirms the sender before anyone acts on the request.
Logs, control results, and the proof auditors and assessors ask for.
CMP-E.1
After an incident, logs are often edited or deleted to hide what happened.
DOR's records cannot be edited or deleted.
CMP-E.2
Screenshots and exports show a control at one moment and can be staged.
DOR records control results continuously as they happen.
CMP-E.3
Organizations attest to controls that have drifted or were never in place.
DOR's record shows what was actually running.
CMP-E.4
Controls can be disabled after an assessment and turned back on before the next.
DOR checks itself and the systems it runs on continuously.
Who signed in, who approved what, and why.
CMP-A.1
Stolen credentials and cloned devices pass most sign-in checks.
DOR confirms the person and the device behind each session.
CMP-A.2
Sensitive changes are made with no record of who approved them.
DOR requires a named approver and keeps the record.
CMP-A.3
People with legitimate access can use it for the wrong reasons.
DOR requires a name and a reason for every sensitive action.
Updates, components, and the attestations vendors hand you.
CMP-S.1
An update can carry harmful code or differ from what was approved.
DOR checks updates before they install.
CMP-S.2
Component lists and attestations can be out of date or wrong.
DOR checks them against what is actually running.
What you keep, what you release, and what you are required to hold.
CMP-D.1
Records can be changed quietly long after they are filed.
DOR proves a record is unchanged since it was created.
CMP-D.2
Records can be purged before their retention period ends or released without approval.
DOR requires a recorded reason for each and respects legal holds.
CMP-D.3
Records sent to regulators, auditors, or partners can be changed after they leave.
DOR's proof travels with every copy.
No entries match. Try another word, or choose All.
Compliance
Bring your next audit, your reporting obligations, and the finding that keeps coming back, or just the question your board keeps asking. DOR will show you exactly where it fits.
