Nothing is edited, only added

Every configuration change, approval, verdict, flag and action is written to an audit log that is only ever added to. It is kept permanently.

Media Verdict console
  1. 01

    Each change is a new line

    A line holds who acted, what they did, the object it concerned, when, the reason where one was given, and an id that follows the work through the services.

  2. 02

    The database refuses changes

    The database itself refuses to update or delete a line of the log, and refuses to empty it.

  3. 03

    A refusal is recorded too

    A request refused on policy grounds is never retried; it is written to the log as a line of its own, with the code that refused it.

  4. 04

    Never deleted

    The retention job, which deletes other data when its time is up, never selects the audit log.

What is recorded

WhatWhat the log holds
Configuration changesEvery change to the installation’s settings, as a new version with its reason and who made it. Each version carries a fingerprint of the one before, checked when the settings are loaded.
ApprovalsEach approval of a response and each release of an external report, with the approver and the reason.
VerdictsEach verdict written, and each analyst’s decision to confirm or overturn it.
FlagsEach time a rule fires, with the rule and what it fired on.
ActionsEach response from draft to the platform’s answer: who drafted, edited, approved and sent it, and when.
Watch list and collectionEach keyword added or removed, and each start or stop of collection, with who did it.
DeletionsOne line for each batch the retention job deletes, with the class of data, the count and the size.
Failures handledEach replay of failed items and each release of a held batch, and each incident raised.

Who can read it

The Audit screen shows the log, behind the same single sign-on as the rest of the console. Reading it is by role.

The Users screen shows each person’s own trail: every write they made, in order.

Service logs are separate from the audit log. They hold no post text, handles, links or user ids, and a daily scan raises an alarm if any appear.

Media Verdict console
IllustrationEach row is one line of the log: when, who, what, on what, and an id. The red block is a request refused on policy grounds, written as a line of its own with the code that refused it.

Taking it with you

  1. 01

    The same rows as data

    Every console screen has a data view with the same fields in the same order, returned page by page in a fixed sort and stamped with the time the data is as of. The Audit screen is one of them.

  2. 02

    From the command line

    The product’s command line prints the same rows as the screen.

  3. 03

    The settings, with their history

    The file of settings versions can be replayed from the start: each version’s fingerprint of the one before is checked, and the rules for who may change what are checked again.

  4. 04

    Nothing to collect in time

    The log is kept permanently, so there is no deadline for taking a copy.

Choose one week and one person, and read their trail on the Audit screen with your auditors.

Request a demo