DPO Radio

Statement of Applicability Workflows

Overview Image

Why It Matters

A Statement of Applicability links a control decision to its rationale and evidence. Forseti helps reviewers prepare that record across the standards the organisation has installed.

Start from the relevant standard's register and inspect what is already documented before adding new rows. Keep the proposed version available for a reviewer to challenge.

The result shows which checks are incomplete and which decisions belong to a person. Review the sources and use the controls on the run to apply the supported proposals you accept.

How It Works

Prepare a first draft

Draft proposed rows against the installed standard, then apply reviewed proposals to a draft version.

Review exclusions

Surface the evidence and rationale behind a proposed exclusion so the reviewer can test it.

Reconcile status against evidence

Compare recorded implementation status with accessible evidence.

Review control and framework applicability

Check privacy and AI control applicability and review which framework conditions apply to the organisation.

Map evidence for reuse

Identify evidence that can support requirements across frameworks, with each use traced to its source.

The Difference

Graphic Image

Without Statement of Applicability Workflows

Graphic Image

With Forseti Statement of Applicability Workflows

IconTeams repeatedly reconstruct a starting position from separate records.
IconPrepare a first draft.
IconA checked exclusion can lack the rationale a reviewer needs.
IconReview exclusions.
IconAn implemented status can survive after its evidence goes stale.
IconReconcile status against evidence.
IconTeams must keep track of applicability across standards manually.
IconReview control and framework applicability.
IconThe same evidence may be collected repeatedly for different reviews.
IconMap evidence for reuse.

Built for Reviewable Compliance Work

Build For Image

Open the evidence behind a recorded implementation status.

Build For Image

Inspect the rationale for an exclusion.

Build For Image

Follow a single evidence item to the frameworks it supports.

Background Image

See Statement of Applicability Workflows in Action

Open the evidence behind a recorded implementation status.

Demo Image
Ronni K. Gothard Christiansen

Ronni K. Gothard Christiansen - Technical Privacy Engineer & CEO

Technical Compliance Expert, 32+ Years Open Source Advocate, X-BoD Open Source Matters Inc.

Or contact via

ronni@aesirx.io+84 909 500 760

Next Steps

Icon Image

Start a pilot

Start a pilot using a versioned Statement of Applicability or supported framework record.

Icon Image

Talk to us

Talk to us about how statement of applicability workflows fits your team's work.

Frequently Asked Questions

The register supports installed ISO/IEC 27001, ISO/IEC 27701 and ISO/IEC 42001. Each can have its own versions and approval record.

Your selected rows go into a draft version for review. An authorised person approves the version in ComplianceOne.

Forseti cites identifiers and uses ComplianceOne's own implementation guidance. The organisation uses its own copy of the standard.

The practitioner run closes with Not checked, Decisions for you, Questions and Re-check when. Review the findings and source references before applying a proposal.

Statement of Applicability Workflows are part of the Practitioner Series on Standard and Enterprise. Access depends on the record type, the user's permissions and any installed framework the workflow needs.