Farshid Ashouri ourway

1 in 1,200: How Rare Cyber Essentials Plus, ISO 27001 and SOC 2 Really Are for Small UK Software Companies (2026 Data)

Last updated 27 September 2026 · Cyber Essentials, Cyber Essentials Plus, ISO 27001, ISO 9001, SOC 2, PCI DSS and IASME Cyber Assurance statistics for the UK, built from government and ISO data rather than vendor marketing.

I run RODMENA, a software company in London, and I run it on my own. The products page lists nearly thirty services, from an authorisation service to a double-entry ledger. So I hear one question from nearly every serious buyer: how do we trust a one-person vendor?

My answer has been certification. I've been putting a lot of hours into Cyber Essentials and Cyber Essentials Plus, and eventually I had to ask whether it would actually set me apart or just tick a box nobody reads. So I went to the primary sources: the UK government's quarterly certification data, the ISO Survey, the government's own evaluation of the scheme, and its

The TRUST5 Method

A methodology for generating correct code through SPEC-driven, quality-gated, self-healing LLM pipelines.

Core Idea

TRUST5 is a method for reliably generating correct code from natural

	# Minimal fast tmux config
	set -g prefix C-a
	unbind C-b
	bind-key C-a last-window

	set -s escape-time 0
	set -g history-limit 50000
	set -g base-index 1
	set -g status-interval 60
	set -g status-right '%H:%M'

	# Alacritty Configuration File (TOML format)

	[general]
	# General Settings
	live_config_reload = true # Automatically reload config changes
	ipc_socket = true # Enable Inter-Process Communication (IPC) (Unix only)

	# Window Configuration
	[window]
	# dynamic_padding = true

	# Alacritty Configuration File (TOML format)

	[general]
	# General Settings
	live_config_reload = true # Automatically reload config changes
	ipc_socket = true # Enable Inter-Process Communication (IPC) (Unix only)

	# Window Configuration
	[window]
	# dynamic_padding = true

	#!/bin/bash

	# Ubuntu Server Cleanup Script
	# Run with: sudo ./cleanup.sh

	set -e

	# Colors for output
	RED='\033[0;31m'
	GREEN='\033[0;32m'

	[2025-10-12 00:56:17,195: INFO/ForkPoolWorker-2] Task tasks.check_for_completed_tickets[4f682d1e-661b-46c6-ac5d-00c542f1bfad] succeeded in 0.0012130020186305046s: None
	[2025-10-12 00:56:22,192: INFO/Beat] Scheduler: Sending due task check tickets every 5 seconds (tasks.check_for_completed_tickets)
	[2025-10-12 00:56:22,193: INFO/MainProcess] Task tasks.check_for_completed_tickets[d936ef88-1c98-4649-abf7-9b67d41150c8] received
	[2025-10-12 00:56:22,194: INFO/ForkPoolWorker-2] Beat: Checking for completed tickets...
	[2025-10-12 00:56:22,194: INFO/ForkPoolWorker-2] Task tasks.check_for_completed_tickets[d936ef88-1c98-4649-abf7-9b67d41150c8] succeeded in 0.0007713509257882833s: None
	[2025-10-12 00:56:27,192: INFO/Beat] Scheduler: Sending due task check tickets every 5 seconds (tasks.check_for_completed_tickets)
	[2025-10-12 00:56:27,194: INFO/MainProcess] Task tasks.check_for_completed_tickets[1ee5defa-0597-4bf5-a4a9-47b2a4da68bf] received
	[2025-10-12 00:56:27,195: INFO/ForkPoolWorker-2] Beat: Checking for completed

	#! /usr/bin/env python3

	from optparse import OptionParser
	from subprocess import check_output, CalledProcessError
	from shlex import quote
	import sys
	import os
	import os.path as path
	import json
	import math

	➜ ffmpeg-docker git:(main) ✗ docker --debug build -t ffmpeg . > error.log
	[+] Building 6.6s (11/15) docker:default
	=> [internal] load build definition from Dockerfile 0.0s
	=> => transferring dockerfile: 2.43kB 0.0s
	=> WARN: FromAsCasing: 'as' and 'FROM' keywords' casing do not match (line 3) 0.0s
	=> [internal] load metadata for docker.io/library/alpine:3.12