Human Risk and Awareness
Vishing and Smishing Simulation
Test independent verification and escalation for voice and SMS requests. Approved scenarios evaluate how impersonation and urgency could influence sensitive changes, disclosure or payment processes.
01 / Overview
Assessment objectives and control obligations
Voice and SMS simulation approves target roles, communication windows, scripts and recording arrangements before execution. Scenarios examine consequential business requests such as support-assisted recovery, supplier-detail changes and payment instructions. Impersonation and urgency are bounded by explicit welfare safeguards and termination criteria.
The exercise records independent callbacks, trusted-source verification, approval segregation and incident escalation without completing financial transfers or uncontrolled account access. Findings identify whether the operating process supports a safe decision under time pressure. Aggregate outcomes preserve language, workload and timing context for proportionate improvement.
02 / Technical analysis
Failure mechanisms and security implications
A callback requirement is ineffective if staff cannot find a trusted number. Results retain language, workload and timing context so improvements address the operating process.
03 / Scope
Technical coverage and authorisation boundaries
Coverage is agreed in writing before testing begins. The rows below describe what this service normally examines. Exclusions, testing windows and escalation contacts are recorded in the rules of engagement.
- Scenario planning
- Approved identity claims, audiences, timing and exclusions.
- Verification
- Callbacks, support checks and sensitive change approvals.
- Outcome review
- Disclosure, actions, reporting and constructive coaching.
- Supporting tools
- Environment-appropriate instrumentation may include Approved voice simulation, Lawful recording, SMS delivery, Reporting evidence. Selection follows the investigative objective, compatibility requirements and approved operating constraints. Automated output requires corroboration against implementation evidence or observed execution before classification as a substantiated finding.
04 / Methodology
Investigation and validation methodology
The exercise is designed around a measurable objective and an agreed adversary scenario. A client control group holds stop authority, and operator activity and defender outcomes are recorded on one timeline.
01
Scenario and authority
Planning
We select relevant behaviours, define success criteria and agree scope, exclusions, deconfliction and staff safeguards.
02
Approve a bounded scenario
Confirm safeguards, recording requirements and termination points.
03
Observe verification decisions
Record responses and assess whether escalation supported a safe outcome.
04
Reconstruction and improvement
Debrief
We correlate the exercise with defender evidence, confirm cleanup and agree improvements with named owners and verification criteria.
05 / Assessment options
Access models and evidential confidence
Supplied access determines investigative reach, validation depth and evidential confidence. The proposal records the access model, supporting material and unresolved coverage limitations; no model implies unrestricted authority or exhaustive verification.
- Black box
- Testing starts without supplied credentials or internal design material. External exposure is examined, while authenticated workflows may remain inaccessible.
- Grey box
- Representative accounts and selected design information support direct comparison of roles, tenants and sensitive workflows.
- White box
- Source, configuration and design evidence support root cause analysis. Runtime and access limitations are still recorded.
06 / Deliverables
Decision-support and verification deliverables
Deliverables distinguish what was observed, what was concluded and where the evidence stops. The agreed scope states which evidence, review sessions and retesting are included.
Executive summary
The summary explains the demonstrated exposure, the business functions affected and the treatment decisions required, including material uncertainty.
Technical findings
Each confirmed issue records the affected assets, prerequisites, reproduction evidence and a specific remediation. Technical severity is presented separately from business priority.
Coverage and limitations
The record identifies the systems, identities and conditions tested, together with exclusions and assumptions that affect interpretation.
Treatment and retest status
Recommendations are sequenced by risk, dependency and ownership. Any agreed retest records resolved, partly resolved and unresolved issues without implying a new assessment.
Service specific evidence
Scenario records and aggregated verification outcomes support process improvements.
07 / References
Applicable technical references
References are selected for the technology and objective in scope, and the edition applied is recorded. A framework mapping supports review; it is not certification or proof of complete compliance.
- NIST cybersecurity and privacy learning guidance
- Revision 1 treats learning as a lifecycle programme with role needs, behaviour change and evaluation. Attendance and isolated campaign rates are not sufficient evidence of lasting improvement.
- NIST digital identity guidance
- Revision 4 authentication guidance informs authenticator lifecycle, assurance, recovery and verifier requirements. Its scope and any binding local obligations are considered explicitly.
- Hong Kong privacy framework
- The Privacy Commissioner explains the PDPO and data protection principles. Technical findings support the organisation and its legal advisers; they do not replace a legal compliance determination.
08 / Safeguards
Operational safeguards and evidence governance
Active work is conditional on written authority from the appropriate asset owner and approved rules of engagement. The operating plan specifies permitted procedures, testing windows, prohibited actions, third-party restrictions and nominated stop authority. Unexpected instability or suspected genuine compromise triggers suspension of affected activity pending the client’s operational decision.
Evidence governance applies purpose limitation, data minimisation and access proportionality to collection, transfer, processing, retention and disposal. The signed terms define authorised recipients and any external processing arrangement. Publication, secondary use and disclosure of client material require the applicable written permission.
Conclusions distinguish substantiated exposure, untested consequence and residual uncertainty. Each material finding identifies the control obligation, causal mechanism, observed outcome and verification criteria for the proposed treatment. Technical severity informs analysis; prioritisation and acceptance of residual risk remain decisions for the client’s authorised risk owner.
No coercive pretexts or real financial transfers. Personal information and recordings follow approved handling terms.
09 / Suitability
Commissioning criteria
Use for finance, support or operational teams handling sensitive requests outside email.
Next step
Define the assessment you need
Tell us the business decision, the systems involved and any operational constraint. We will explain the coverage proposed, the access required and the evidence the engagement can provide.
- Confidentiality first
A mutual confidentiality agreement is signed before any technical detail is exchanged, so scope discussions can happen safely.
- Scope and cost in writing
Deliverables, access expectations, timeline and fee are confirmed before the engagement begins, and a scope change needs agreement.
- Answered by the delivery team
The consultants who scope an engagement are the consultants who perform it and explain the result to your team.
Related services
