Security & integration / Audit

Audit

Audit capture is part of WebFrolic’s architecture, not a feature added later: no action can happen without being recorded. Every action on every resource is kept in an immutable trail with user, session and device context, and identity flows are recorded as linked transactions.

Available now in WebFrolic.

Why it matters

Evidence collected after an incident is evidence you do not have.

When audit is bolted on, gaps appear exactly where investigations need detail. Built-in, immutable records with session and device context turn compliance questions into a search.

Immutable

Every action, every resource

Records cannot be quietly changed; sensitive records are signed.

Context

User, session and device

Every record carries who acted, in which session and from which device.

Linked

Transactions and reasons

Flows are recorded as related transactions; notes, tickets and requests explain changes.

Compliance evidence

Answers auditors ask for.

QuestionWhere the answer isRead more
Who changed this role?The role’s Audit tab.Roles
What did this person do?The person’s Activity tab and transaction log.Transactions
Why was access granted?The request, approval workflow and note on the grant.Access workflows
Who looked at this customer?Support actions recorded against the assigned ticket.Support desk
Who used the shared account?Service-user actions record the original user and session.Service users

Before rollout

Questions worth answering.

Settle these first and the rollout is mostly configuration.

  • Decide which changes require a note.
  • Know where each audit question is answered.
  • Review privileged and support activity regularly.
  • Use the Audit and Activity tabs in every access review.
  • Check that every integration acts as an accountable identity.

Related capabilities

Explore what connects to this.

These capabilities are usually configured together.

Evaluate with your scenario

Start with a concrete workflow.

Share the identities, resource boundary and decision you want to test. The walkthrough can focus on the relevant behavior rather than a generic feature tour.