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.
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.
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.
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.
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.
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.
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.
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.