Monday, August 24, 2026

    How often each control is actually tested

    The catalog declares a test procedure for every control it carries and a cadence for none of them. Continuous is precisely what a design-time catalog cannot express — so it has to be declared, per control, with the evidence source that makes the test re-performable.

    What this studio does

    Every control in the governance catalog already carries a test procedure and examples of the evidence it would produce. What none of them carries is a cadence — so the catalog can describe a control in full and still not say whether it is checked once a year or continuously. This studio composes that missing layer: how often, over what population, from which system, owned by whom.

    It refuses the shortcuts that would make it look more decisive than it is. Whether a TEST runs by machine is declared rather than read off the control’s own automation mode, because how a control operates is a different question from how it is checked. Coverage is reported as a number rather than as one finding per uncovered control. And no test has run: producing results needs the GRC and ERP systems the client operates, which is stated on the page rather than left to be inferred from an empty column.

    Access code required

    The full working surface — and every other Transform suite asset — opens with one access code.

    Access codes expire after 24 hours, and this one is remembered in this browser only. Sign in once and the unlock follows your account to every device you use.

    Sign in

    Sign in

    Use your email or Google account — your unlock then follows your account instead of this browser.

    or