SEE WHAT USEFUL WORK LOOKS LIKE

Clear findings.
Practical next steps.

Explore the kind of information an engagement can provide before you decide what support you need.

Illustrative samples, not client work.

Every example below uses a fictional scenario. It is not a testimonial, a claim about a real organisation or a guarantee of the content or outcome of your engagement. Scope and deliverables are agreed with you.

FICTIONAL EXAMPLE / CONSULTATION

A practical security action plan

Scenario: A fictional small team wants to improve shared account access and recovery.

What the client receives: A written set of priorities, owners and next steps.

Illustrative observations and next actions
PriorityObservationPractical action
FirstTwo people share an account without a recovery owner.Assign an accountable owner, use individual access where supported and document recovery.
NextBackups exist but have not been tested.Agree a safe restore exercise and record what can actually be recovered.

Priority: account recovery. Owner: designated operations lead. Evidence: walkthrough of current practice using fictional data. Next action: confirm ownership and test the agreed recovery process.

Coverage and limits: Advice only. Configuration changes and technical testing require a separate agreed scope.

FICTIONAL EXAMPLE / SECURITY ASSESSMENTS

An evidence-led security review

Scenario: A fictional organisation wants to check access controls and backup readiness.

What the client receives: Coverage, observations, evidence limitations and a prioritised improvement plan.

Illustrative observations and next actions
PriorityObservationPractical action
High priorityDeparted staff still appear in the access inventory.Validate the records with the system owner, remove unnecessary access and document the offboarding process.
Follow-upNo recent restore test is documented.Conduct an agreed restore exercise and retain its results.

Review coverage: supplied access inventory and recovery procedures. Limitation: this review did not attempt exploitation or inspect every system. Verify each observation with the responsible owner before changing production.

Coverage and limits: A review of agreed controls is distinct from a penetration test and is not a compliance certification.

FICTIONAL EXAMPLE / PENETRATION TESTING

A penetration testing report excerpt

Scenario: A fictional staging application has two test roles and an owner-approved test window.

What the client receives: Executive summary, agreed coverage, validated findings, business impact, remediation and retest status.

Illustrative observations and next actions
PriorityObservationPractical action
High · illustrativeA synthetic support role can access an object outside its assigned tenant.Enforce object-level authorisation on the server and add isolation tests for every relevant route.
RetestThe sample fix has not yet been independently verified.Repeat the agreed test with separate synthetic accounts and record the outcome.

Finding PT-01 — tenant isolation. Evidence: two synthetic accounts and a single fictional record in an authorised lab. Impact: an equivalent production weakness could expose another tenant’s information. Retest status: pending. Severity depends on the actual environment and evidence.

Coverage and limits: This is a fictional example, not a finding about a real client or this website. Real testing requires written authorisation, rules of engagement and agreed evidence handling.

FICTIONAL EXAMPLE / AI SAFETY

An AI-use and safeguards review

Scenario: A fictional team wants to use an assistant to draft customer responses.

What the client receives: Use-case inventory, practical handling rules, risk observations and a human-review workflow.

Illustrative observations and next actions
PriorityObservationPractical action
Before rolloutThe team has not agreed which information may be sent to the assistant.Define approved data categories and keep confidential or personal records out until the appropriate safeguards are agreed.
Human reviewDraft answers could be sent without checking their accuracy.Require a responsible person to verify facts, recipients and proposed actions before sending.

Example rule: use fictional or approved public inputs for initial trials. Treat generated responses as drafts. Check facts against an authoritative source. Do not grant autonomous sending or system access without a separately reviewed control.

Coverage and limits: A practical safeguards review does not certify an AI model as safe or guarantee that it cannot fail.

FICTIONAL EXAMPLE / AWARENESS TRAINING

A focused training plan

Scenario: A fictional team needs practical help recognising impersonation and protecting accounts.

What the client receives: Learning objectives, relevant examples, guided exercises and take-away actions.

Illustrative observations and next actions
PriorityObservationPractical action
Learning goalParticipants need a repeatable way to check an unexpected payment request.Practise stopping, verifying through a known channel and reporting the attempt.
PracticeAccount recovery is unfamiliar.Use a safe demonstration with fictional accounts and discuss the organisation’s actual reporting route.

Session outline: recognise the situation; practise a safe response; discuss a fictional scenario; explain the next action in your own words. Feedback measures understanding, not a promise that incidents will stop.

Coverage and limits: Examples are educational. Simulated phishing or live-system exercises are included only when separately authorised.

FICTIONAL EXAMPLE / GUIDED IMPROVEMENTS

A controlled improvement and handover plan

Scenario: A fictional owner has agreed recommendations and wants help implementing them.

What the client receives: Change plan, responsibilities, verification steps, rollback arrangements and handover notes.

Illustrative observations and next actions
PriorityObservationPractical action
PrepareA change could affect sign-in or recovery.Confirm a tested recovery route and an agreed maintenance window before starting.
VerifyThe owner needs evidence that the intended control works.Record the agreed checks, explain the outcome and document remaining limitations.

Change: strengthen access protection. Prerequisite: owner-approved scope and verified recovery route. Verify: expected sign-in and recovery behaviour. Handover: owner responsibilities, recovery steps and unresolved items.

Coverage and limits: The owner retains control of their accounts. No unapproved production changes are implied.

FICTIONAL EXAMPLE / ONGOING ADVISORY

An advisory review and decision log

Scenario: A fictional business wants periodic guidance as its tools and team change.

What the client receives: Agreed review rhythm, decision log, current priorities and follow-up responsibilities.

Illustrative observations and next actions
PriorityObservationPractical action
ReviewA new supplier may receive sensitive business information.Document the intended data flow, review relevant safeguards and assign the decision owner.
TrackPrevious recommendations need a clear follow-up status.Record completed, deferred and pending actions with reasons and owners.

Decision log: concern, available evidence, options, agreed decision, owner and next review point. Urgent incident response is not assumed to be part of routine advisory support.

Coverage and limits: Availability, response expectations and deliverables are agreed in the engagement; this is not an implied 24/7 response service.

Start with your situation.

Tell us what you want to protect or improve. We will help define a useful scope and confirm deliverables before work begins.

Book a service