K Ocean Technology

Security Risk Assessment and Audit (SRAA) in Hong Kong

A Security Risk Assessment and Audit (SRAA) identifies what could go wrong with an IT system and checks whether its security controls meet agreed requirements. K Ocean helps Hong Kong organisations decide which gaps to fix first and what evidence to keep for management, procurement or audit review.

When should you consider an SRAA?

  • Before launching a system or making a major change, such as moving it to the cloud.
  • When onboarding a service provider that will operate a critical system or handle sensitive data.
  • When a tender, contract, internal policy or applicable requirement calls for a security review.
  • When management needs a clear picture of risks across a system already in use.

What you receive

  • A management summary showing the risks that need a decision.
  • An assessment report documenting the scope, evidence, findings, risk ratings and limitations.
  • A prioritised remediation plan showing recommended fixes and any outstanding issues.

Where follow-up is in scope, we review evidence for agreed fixes and record what was verified and what remains open.

Frequently asked questions

What is the difference between a security risk assessment and a security audit?

A risk assessment looks at threats, weaknesses, likelihood and business impact to decide what needs attention. A security audit compares controls and available evidence against agreed criteria. An SRAA can bring both views into one engagement.

Is SRAA the same as penetration testing?

An SRAA reviews security risks and controls across the agreed system. Penetration testing uses authorised technical testing to validate selected weaknesses and attack paths. It can support an SRAA when included in scope. See K Ocean’s penetration testing service.

Can an SRAA be scoped to Hong Kong government requirements?

For work involving a Hong Kong government system, share the tender or contract and the applicable security documents at the start. We can discuss mapping the scope, evidence and reporting to the specified criteria. The Digital Policy Office publishes the government Practice Guide for Security Risk Assessment & Audit (ISPG-SM01). The commissioning organisation determines its acceptance requirements.

How long does an SRAA take, and what affects the cost?

Timing and fees depend on the number and complexity of systems, the criteria to be assessed, how readily evidence can be obtained, and whether testing or follow-up is included. To start scoping, share the system list, any required criteria and your target date.

Do we also need a Privacy Impact Assessment?

Consider a PIA if the project changes how you collect, use, share or retain personal data and could affect individuals’ privacy. SRAA and PIA cover different questions and can be scoped together. See K Ocean’s Privacy Impact Assessment service.

Should we review security before switching IT providers?

Start before the handover if the provider manages systems you depend on. Confirm who will take over administrator accounts, how the new team will verify that it can restore a backup, and when the outgoing provider’s access will be removed. An SRAA can cover these handover risks and the evidence needed to close them.

Planning a go-live or responding to a tender? Share the systems involved, your target date and any specified requirements so we can discuss the scope.

Talk to K Ocean