DEV Community

Erkki Laine
Erkki Laine

Posted on

VITI Engineering Guide: The "Machine Reality" Matrix (Or How to Replace Your ITIL Priests with 5 Lines of Code)

Another dispatch from the VITI Magazine Editorial Board and VITI Labs.

If you have survived reading our previous VITI Memos, you already know the truth: Enterprise IT is drowning in process theater. CAB meetings, 300-page TOGAF blueprints, and Word-based security policies are simply illusions of control.

In the Business Impact Governance Framework (BIGF), we replace the "ITIL Priesthood" with Machine Reality. We move from Policy-as-Document to Policy-as-Code.

To demonstrate how little code it takes to replace a corporate bureaucracy, VITI Labs has compiled the definitive Machine Reality Matrix. We have taken the most common ISO 27001, DORA, and NIS2 requirements and translated them from manual liturgy into deterministic runtime logic.


The Machine Reality Matrix

Control / Regulation The ITIL Priest's Meeting Theater BIGF: Policy-as-Code How the Machine Handles It
ISO A.8.24
Encryption
Write on the Intranet: "Please remember to encrypt databases." Hope for the best. if db.encrypted == false { reject_deployment() } The machine refuses to spin up an unencrypted database. You cannot "forget" the guideline.
ISO A.8.12
Change Management
Create a Jira ticket, wait for Tuesday's CAB meeting, and beg the committee for a stamp. if repo.pr.approvals < 1 { block_release() } CAB is replaced by code. If the code lacks a peer review, it does not move to production. Period.
ISO A.8.20
Network Security
Draw a Visio map of the network once a year for the auditor. if fw.ports.contains(22) && network.public { trigger_hard_halt() } Instant response. If someone opens an SSH port to the public internet, the machine shuts it in milliseconds.
Custom Rule:
Weekend Peace
Send an email on Friday: "Hey team, please try to avoid prod deployments this weekend!" if time.is_weekend() && change.risk == "high" { exit(1) } The ruthless rules engine. The machine checks the clock—it automatically slams the pipeline shut on Saturday.
Custom Rule:
Access Control
An Excel sheet where the Risk Manager marks who can read what, updated monthly. if agent.token.signature != valid { deny_access() } Cryptographic enforcement. Agents and users are verified in real-time; no Excel guesswork.
DORA (Art. 11)
Vulnerability Mgt
Run a scan once a month, export to PDF, and email the board of directors. if image.vuls.severity("critical") > 0 { reject_build() } Continuous conformance. If the container image has a critical CVE, it never even reaches the test environment.
DORA (Art. 26)
3rd Party Risk
Send the vendor a 50-page Word security questionnaire and hope they don't lie. if supplier.api.score < 80 { sandbox_traffic() } Real-time API monitoring. If the vendor starts leaking or stalling, traffic is automatically sandboxed.
NIS2 (Art. 21)
Supply Chain Security
Add a clause to the contract: "Vendor commits to NIS2 compliance." if artifact.signature != official_vendor_key { block_execution() } Cryptographic supply chain. If the artifact lacks the official signature, the machine will not execute it.

Why This Changes Everything

  1. Rules are Binary: There is no such thing as "roughly encrypted" or "almost reviewed." A condition is either True or False. The machine does not compromise.
  2. The Code is the Document: The code snippets in the matrix above are the official corporate security policy. You do not need to write it in Word, because the code itself is the rule being enforced.
  3. Automated Audit Logs: When every change runs through these deterministic gates, BIGF collects Canonical Decision Records (CDRs). It generates a read-only, immutable cryptographic evidence trail proving to the auditor that the law was obeyed every single second.

A Question for the Priesthood

When it is this blatantly obvious how easily these controls can be automated and strictly enforced, why does the ITIL Priesthood still fiercely defend their Tuesday CAB meetings?

Is it simply a lust for bureaucratic power, or do they genuinely lack the technical competence to trust the code?

VITI Labs suspects it is the former. When the machine takes over the governance, the priests lose their pulpit.

just google it: big framework erkki laine

Top comments (0)