← 返回考试

免费学习指南

Cybersecurity Auditor (OCCA) — Free Curriculum

This free curriculum covers every domain assessed in the Oxford Certified Cybersecurity Auditor (OCCA) examination: governance and risk, frameworks, controls, audit evidence and reporting, and the main technical audit areas. Read each chapter carefully, note the key points, and then sit the 90-question examination.

准备好了吗?开始免费考试 110 分钟 · 90 道题
第 1

The role of the cybersecurity auditor

A cybersecurity audit provides independent, objective assurance to management and the board on whether security controls are designed appropriately and operating effectively. Auditors do not fix problems or operate controls themselves; doing so would impair their independence. Instead, they evaluate risk, test controls, report findings and follow up on agreed actions.

Every engagement starts with an audit plan or engagement letter defining objectives, scope, criteria, timing and reporting lines. A risk-based approach concentrates effort on the areas with the highest inherent risk to business objectives rather than spreading effort equally or testing only what is easy.

Professional conduct is essential: independence, objectivity, confidentiality, due professional care and professional scepticism — a questioning mind that critically assesses evidence without being hostile.

  • Assurance, not implementation: auditors evaluate, they do not operate controls
  • Plan the engagement: objectives, scope, criteria, timing
  • Focus on the highest risks
  • Independence, objectivity, confidentiality and scepticism
要点: An auditor's value lies in being independent, evidence-based and risk-focused.
第 2

Governance, risk and risk treatment

Security governance defines who is accountable, the policies that apply, the organisation's risk appetite and how leadership oversees cybersecurity. The board or audit committee needs independent assurance because it is accountable for risk oversight.

Inherent risk is the risk before controls; residual risk is what remains after controls. Risk treatment options are: mitigate (reduce with controls), transfer (insurance or contracts), avoid (stop the activity) or accept (within the approved risk appetite, documented by the risk owner). Ignoring a risk without a recorded decision is not a valid treatment.

Key risk indicators (KRIs), such as the number of unpatched critical vulnerabilities, show when exposure is rising. Continuous control monitoring tests key controls frequently and provides earlier warning than periodic audits alone.

  • Governance = roles, policies, risk appetite, oversight
  • Inherent risk before controls; residual risk after controls
  • Treat risk by mitigating, transferring, avoiding or accepting — never by ignoring
  • Risk owners in the business accept risks, not auditors
  • KRIs and continuous monitoring give early warning
要点: Risk decisions belong to accountable owners; the auditor tests whether those decisions are informed and implemented.
第 3

Security frameworks and standards

ISO/IEC 27001 specifies requirements for an information security management system (ISMS). Organisations assess risk, select controls (Annex A) and document them in a Statement of Applicability, which states whether each control applies and justifies exclusions. Certification scope matters: a certificate covering one data centre gives little assurance about services outside that scope. The management system improves continually through the Plan-Do-Check-Act cycle.

The NIST Cybersecurity Framework 2.0 organises outcomes into six functions: Govern, Identify, Protect, Detect, Respond and Recover. The CIS Critical Security Controls are a prioritised, voluntary set of technical safeguards. SOC 2 reports, issued by independent auditors, give assurance about a service organisation's controls relevant to security, availability, processing integrity, confidentiality and privacy. A Type I report assesses design at a point in time; a Type II report also tests operating effectiveness over a period.

  • ISO/IEC 27001: ISMS requirements, risk-based control selection, Statement of Applicability
  • Always check the scope of a certificate
  • NIST CSF 2.0: Govern, Identify, Protect, Detect, Respond, Recover
  • CIS Controls: voluntary, prioritised safeguards
  • SOC 2 Type II tests operating effectiveness over time
要点: Frameworks give structure and criteria — but the auditor must still test what actually happens.
第 4

Control types and control testing

Controls can be classified by purpose: preventive (stop an incident, e.g. MFA), detective (identify it, e.g. intrusion detection or log review), corrective (restore, e.g. recovery from backup), deterrent and directive. They can also be classified by nature: administrative or managerial (policies, screening, training), technical (firewalls, encryption) and physical (locks, guards). A compensating control is an alternative that reduces the risk when the primary control cannot be implemented.

Auditors first test design — would the control, operated as described, address the risk? — and then operating effectiveness — did it work consistently throughout the period? Testing techniques include inquiry, inspection, observation and re-performance. Inquiry alone is not sufficient evidence of effectiveness.

  • Preventive, detective, corrective; administrative, technical, physical
  • Compensating controls cover gaps when primary controls are not possible
  • Design effectiveness first, then operating effectiveness
  • Combine inquiry with inspection, observation or re-performance
要点: A control that looks good on paper is only effective if evidence shows it works in practice.
第 5

Audit evidence, sampling and findings

Evidence must be sufficient and appropriate. Evidence obtained directly by the auditor — re-performance, system reports verified by the auditor — is more reliable than verbal statements or undated screenshots. Before sampling, confirm that the population is complete; then select a representative sample so that conclusions can be extended to the whole population.

If exceptions are found — for example, 6 of 25 sampled accounts lacked approval — the control is not operating effectively. Do not keep enlarging the sample until results look acceptable. A finding should state the condition (what was found), criteria (what should be), cause, effect (risk) and recommendation. Management owns the corrective actions, with owners and target dates, and follow-up audits verify implementation.

Work papers must allow another experienced auditor to understand and re-perform the work. Scope limitations must be documented and their effect on the opinion reported.

  • Prefer auditor-obtained evidence over statements
  • Confirm population completeness before sampling
  • Condition, criteria, cause, effect, recommendation
  • Management fixes; auditors follow up
  • Document limitations and keep re-performable work papers
要点: Conclusions are only as strong as the evidence behind them.
第 6

Identity and access management audits

Access control audits examine joiner, mover and leaver processes, user access reviews, privileged access and segregation of duties. Active accounts of former employees indicate that de-provisioning is failing. Periodic access reviews confirm each user's access remains appropriate for their role.

Privileged accounts must be few, individually assigned, protected with MFA, monitored and reviewed; just-in-time elevation and session logging reduce risk. Generic or shared accounts undermine accountability. Segregation of duties prevents one person from completing a sensitive process alone — for example, creating a supplier and approving payments to it. Multi-factor authentication is the most direct control against credential-stuffing.

  • Joiner–mover–leaver processes must be timely and evidenced
  • Review access regularly with business owners
  • Privileged access: few, named, MFA, monitored, just-in-time
  • Avoid shared accounts
  • Enforce segregation of duties in critical processes
要点: Excessive or forgotten access is one of the most common audit findings — and one of the most exploited.
第 7

Change, configuration and vulnerability management

Change management ensures changes are authorised, tested, approved and documented before reaching production. The best evidence of approval is a change record approved by an authorised person before implementation. Emergency changes still need retrospective review and documentation. Developers with unrestricted production access create the risk of unauthorised or untested changes.

Configuration baselines (hardening standards) define the secure state of systems; drift reviews detect deviations. Vulnerability management relies on a complete asset inventory, regular scanning and remediation prioritised by severity (for example CVSS), exploitability and asset criticality, within defined timelines. Penetration tests go further than scans by attempting exploitation to show real impact, under agreed rules of engagement covering scope, timing, techniques, contacts and authorisation.

  • Approval before implementation; emergency changes reviewed afterwards
  • Separate development from production access
  • Hardening baselines and drift detection
  • Asset inventory first; prioritise by severity and criticality
  • Penetration tests need written rules of engagement
要点: Unmanaged change and late patching turn known weaknesses into incidents.
第 8

Logging, monitoring and incident response

Centralised logging (for example in a SIEM) allows events to be correlated and protects logs from tampering. Important events include privileged logins, security configuration changes and account creation or deletion. Accurate time synchronisation supports investigations, and retention periods must meet investigative, legal and compliance needs. Thousands of uninvestigated alerts indicate poor tuning; detection rules should be tuned and alerts prioritised by risk.

Incident response following NIST SP 800-61 includes preparation; detection and analysis; containment, eradication and recovery; and post-incident activity. Auditors expect defined roles, decision authority, escalation and communication procedures (including regulators where required), severity classification, evidence preservation with chain of custody, regular exercises and lessons-learned reviews focused on root causes rather than blame.

  • Centralise, protect and time-synchronise logs
  • Tune alerts so analysts investigate what matters
  • Incident phases: prepare, detect and analyse, contain/eradicate/recover, learn
  • Define who can make critical decisions during an incident
  • Preserve evidence and test the plan
要点: Detection without investigation, and plans without exercises, give false comfort.
第 9

Business continuity, disaster recovery and backups

A business impact analysis identifies critical processes and the impact of disruption over time, which sets recovery time and recovery point objectives. Business continuity plans keep critical business functions running; disaster recovery plans restore IT systems and data.

Plans must be current and tested. An untested plan, or one written for an environment that no longer exists, gives no reliable assurance. Backups must be restored in tests to prove they work. Immutable or offline copies, separated from production credentials and networks, protect against ransomware encrypting the backups too.

  • BIA drives recovery objectives
  • BCP = business functions; DRP = IT recovery
  • Test plans regularly and update them after changes
  • Test restores, not just backup jobs
  • Keep immutable or offline backup copies
要点: Recovery capability is proven only by testing.
第 10

Third-party, cloud and data protection risk

Third-party risk management begins before contract signature with due diligence proportionate to risk, continues with contractual security and right-to-audit clauses, and includes ongoing monitoring. Independent reports such as SOC 2 Type II or ISO 27001 certificates provide assurance, but auditors must check their scope and the complementary user entity controls the customer must operate. Shadow IT — cloud services bought without IT involvement — creates unmanaged data storage and access.

In the cloud, customers remain responsible for configuration and identity; misconfigured IAM is a leading cause of breaches. Under the GDPR, organisations apply principles such as data minimisation, perform Data Protection Impact Assessments for high-risk processing and notify the supervisory authority of qualifying personal data breaches within 72 hours. Data classification ensures protection proportionate to sensitivity, and encryption keys must be generated securely, restricted, rotated and kept separate from the data.

  • Due diligence, contracts and monitoring for suppliers
  • Read SOC reports carefully, including user entity controls
  • Customers own cloud configuration and IAM
  • GDPR: minimisation, DPIAs, 72-hour breach notification
  • Classify data and manage keys securely
要点: Outsourcing a service does not outsource accountability for the risk.
第 11

Reporting and communicating results

Audit reports must be clear, concise, objective and prioritised by risk, explaining business impact rather than only technical detail. Each finding includes agreed management actions with owners and target dates. The overall opinion may be unqualified (effective), qualified (effective except for specific significant weaknesses) or adverse.

Auditors must resist pressure to remove or downgrade accurate findings; management's views are included through the formal response process. Results are reported to the audit committee or board, who oversee risk. Security awareness effectiveness should be evaluated by behaviour — phishing simulation and reporting rates — rather than attendance alone.

  • Clear, objective, risk-prioritised reporting
  • Management actions with owners and dates
  • Choose the opinion the evidence supports
  • Never suppress accurate findings
  • Report to those accountable for oversight
要点: A clear, honest report is how audit work turns into real improvement.

准备好了吗?开始免费考试

免费参加考试并获得数字徽章。通过后可选择订购正式证书。

开始免费考试