Adversary Emulation & Threat Research

Makes risk measurable, fundable and defensible.

COFFSec is an offensive security firm based in Hong Kong. Through penetration testing, adversary emulation and specialist security reviews, we investigate how attackers could compromise critical systems and business processes. Our assessments provide technical evidence for managing strategic, operational, financial and compliance risk, with clear findings, practical remediation and explicit limitations.

Who we are

Mission

Provide independent offensive security evidence that helps organisations protect critical assets, prioritise remediation and make informed risk decisions.

Vision

A security practice in which technical assurance supports business resilience, responsible investment and effective risk oversight.

Values

Professional independence, lawful authorisation and careful handling of client information guide our work. Conclusions reflect the evidence, including uncertainty and assessment limits.

Certifications
Offensive Security certification badge
Offensive Security certification badge
Offensive Security certification badge
Offensive Security certification badge
Offensive Security certification badge
Offensive Security certification badge
Offensive Security certification badge
Offensive Security certification badge
Offensive Security certification badge
Offensive Security certification badge
Offensive Security certification badge
Offensive Security certification badge
Offensive Security certification badge
Offensive Security certification badge
Offensive Security certification badge
Offensive Security certification badge
Strategic · Operational · Financial · Compliance risk

Our offensive assessments establish how a technical weakness could affect a business objective. We identify the control involved, demonstrate the exposure within authorised limits and provide evidence for remediation priorities, investment decisions and the acceptance of residual risk.

Hong Kong threat context

Reported incidents in Hong Kong

HKCERT publishes monthly counts of incidents reported to the centre, including phishing, malware, unauthorised access and denial of service. The series provides regional context for threat assessment and scenario selection. Reporting volumes are influenced by public awareness, reporting practices and campaign activity. They do not establish an individual organisation’s likelihood of compromise or measure the effectiveness of its controls. Use these figures alongside your asset exposure, incident history and assessment evidence.

Published data
October 2026
Reporting year

Reported incidents

1,2656%month on month
Year to date · 2026
14,027
Average per published month
1,403
Same month last year
1,154 · +10%
62%

Share of month

Phishing

787

Monthly incident reports2026

By reported incident type
JanFebMarAprMayJunJulAugSeptOct04509001.4k1.8k
BotnetDistributed Denial-of-serviceMalwarePhishingWeb Defacement/IntrusionOthers

Highest monthly total · July 2026 · 1,775

Hover over or select a month to view its figures

Incident types for the selected month

Share of monthly total
Phishing78762%
Botnet21017%
Others20816%
Malware514%
Web Defacement/Intrusion81%
Distributed Denial-of-service10%

Threat-led assurance regimes

Regulated attack simulation

Threat-led penetration testing is defined by supervisory authorities rather than by the firms that supply it. Each regime below prescribes which institutions fall within its population, what intelligence must substantiate the scenario, and what evidence the institution is obliged to produce. We map an engagement onto the regime that governs it, so that the resulting assurance withstands supervisory scrutiny rather than merely satisfying an internal programme.

Select a framework

01 / 15

HK · Hong Kong

Standing

Mandatory for authorized institutions rated medium or high for inherent risk

Population
Authorized institutions assessed under the C-RAF; applicability follows from the inherent-risk rating assigned to the institution
Cycles
Runs in step with the framework assessment and recurs at each maturity review
Roles
An iCAST manager, a threat-intelligence specialist and testers, each qualified against CREST-mapped requirements

Governing authority

Hong Kong Monetary Authority, within the Cybersecurity Fortification Initiative (CFI 2.0)

Introduced 2016; revised 2020

HKMA · Cybersecurity Fortification Initiative 2.0

iCAST

Intelligence-led Cyber Attack Simulation Testing

Hong Kong situates attack simulation within a supervisory assessment of the institution as a whole, so the exercise inherits both the inherent-risk rating that triggered it and the maturity level the institution is expected to attain.

Threat intelligence is tailored to the Hong Kong banking sector, and every scenario specifies the compromise outcome sought against a named critical service — data insertion, loss of integrity or privilege escalation among them. Since CFI 2.0, detection and response are measured while the red team is still operating, and testers must hold qualifications mapped to recognised certifications. The closing report binds each scenario to a remediation plan the institution itself owns.

Test phases

  1. 01

    Preparation and scoping

  2. 02

    Tailored threat intelligence

  3. 03

    Scenario design

  4. 04

    Execution under blue-team observation

  5. 05

    Closure and remediation plan

Advances every ten seconds

National TIBER guides also apply in European Central Bank implementation index

Austria, Belgium, the Czech Republic, Denmark, Estonia, Finland, France, Greece, Iceland, Ireland, Liechtenstein, Luxembourg, Malta, Norway, Portugal, Romania, Slovakia and Sweden.

Offensive security services

Technical depth. Business relevance.

Our services cover applications, infrastructure, cloud platforms, identity, adversary emulation, AI, physical environments and human risk. Each engagement connects a defined attack scenario to the assets and business processes it could affect. Strategic risk includes exposure introduced by acquisitions, new services and platform change. Operational risk concerns disruption and recovery. Financial risk includes fraud, asset loss and response costs. Compliance risk concerns the controls and evidence required by applicable obligations. These perspectives guide reporting without replacing the technical investigation.

View all services

Attack paths often cross disciplines. Scope is agreed around the systems, trust relationships and business objectives involved.

Assessment methodology

From attack paths to risk decisions

We establish the attacker’s starting position, test the relevant security boundaries and explain the observed business consequence. Findings distinguish confirmed effects from plausible outcomes that remain untested. Technical severity, business priority and residual risk are considered separately, with the assumptions behind each conclusion made explicit.

Defined objectives and coverage

Scoping identifies critical services, sensitive information, relevant threats and the decision the assessment will support. The plan records identities, environments, exclusions and operational safeguards before testing begins.

Evidence with technical context

Findings retain the affected version, required privileges, test sequence and observed result. Review challenges the root cause, impact and corrective guidance. Variable behaviour and gaps in evidence remain visible.

Treatment and verification

Recommendations identify controls that interrupt the attack path and dependencies that affect implementation. Retesting verifies agreed changes. Projected risk reduction is distinguished from reduction supported by completed remediation and verification; acceptance remains with the client’s authorised risk owner.

Interlocking wireframe planes forming a chain of connected nodes

Authority chain

  1. Threat scenario
  2. Control validation
  3. Business impact
  4. Risk treatment

The assessment links technical evidence to a documented risk scenario and a verifiable corrective action.

Professional references

Recognised guidance. Explicit limitations.

Technical methods draw on OWASP, NIST and MITRE guidance appropriate to the environment. Risk reporting is informed by NIST guidance on enterprise risk management and concepts reflected in the recognized information security frameworks, including asset protection, least privilege, control effectiveness and due diligence.

Hong Kong skyline at dusk seen from a high floor

Hong Kong · adversary research

Professional responsibility

Clear authority. Accountable delivery.

Offensive testing introduces controlled activity into systems that support real operations. The engagement plan identifies delivery responsibilities, review arrangements and the client contacts authorised to approve changes or stop work. Technical judgement remains independent of commercial pressure.

Technical review

Review checks whether the evidence supports the stated impact, whether prerequisites are clear and whether remediation addresses the underlying control failure.

Written authorisation

Assets, permitted techniques, operating windows and escalation procedures are agreed before active testing. Third party permissions are confirmed where required.

Protected client information

Evidence collection is limited to the assessment purpose. Access, transfer, processing, retention and deletion follow the agreed terms. Publication or reuse requires separate written permission.

Commission an assessment

Define the risk. Validate the controls.

Identify the service, information asset or business process requiring assurance. Consultation examines relevant attack scenarios, available access and operating constraints, resulting in a proposal with defined coverage, deliverables and verification criteria.

Scope and objectives

Identify the business concern, relevant systems and evidence required. Select testing, review or investigation according to the question and the operational risk.

Authority and preparation

Confirm ownership, permissions, representative accounts, safety limits and information handling. Resolve material dependencies before scheduling active work.

Assessment and handover

Validate the agreed scenarios, communicate urgent exposure and deliver reviewed findings. Explain remediation priorities, assessment limitations and the scope of any agreed retest.

Scope, scheduling and service commitments are confirmed in the engagement agreement.

We value your privacy

We use essential cookies to keep the site working and analytics cookies to understand how you use it, so we can improve. We do not sell your data. See our Privacy Policy for details.