← 返回考试

免费学习指南

Ethical Hacker & PenTester — Free Curriculum

This free curriculum covers every domain assessed in the Oxford Certified Ethical Hacker & PenTester examination: ethics, law and scoping, methodologies, reconnaissance, scanning and enumeration, vulnerability analysis, web application security, authentication and sessions, network, Active Directory, wireless and cloud security, social engineering and physical testing, adversary emulation, disclosure, reporting and defensive recommendations. Read each chapter, note the key points, and then sit the 100-question examination.

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

Ethics, law and authorisation

Ethical hackers differ from malicious attackers because they have explicit written authorisation and work within an agreed scope to improve security. Testing without authorisation — even with good intentions — can breach computer misuse laws such as the UK Computer Misuse Act or the US CFAA. NDAs protect client information, and testers handle any sensitive data with minimal access, secure storage and agreed deletion.

Professional conduct means integrity, confidentiality, staying in scope and honest reporting. Gaining administrator access never extends scope automatically, and anything outside scope — such as a third-party service on the same server — requires clarification and authorisation first.

  • Written authorisation is mandatory
  • Computer misuse laws
  • Confidentiality and data handling
  • Scope never expands automatically
要点: Authorisation is what makes hacking ethical.
第 2

Scoping and methodology

Rules of engagement define targets, permitted techniques, timing, contacts and handling of critical findings, including immediate reporting of evidence of existing compromise. Aggressive scans on production need agreed timing. Black box testers have little prior knowledge; white box testers receive architecture, credentials or source code.

A vulnerability assessment identifies and prioritises weaknesses; a penetration test proves impact through controlled exploitation. Recognised methodologies include PTES, the OWASP Web Security Testing Guide and NIST SP 800-115. Phases run from pre-engagement through reconnaissance, scanning and enumeration, vulnerability analysis, exploitation, post-exploitation and reporting.

  • Rules of engagement
  • Black, grey and white box
  • Assessment vs penetration test
  • PTES, OWASP WSTG, NIST 800-115
  • Standard test phases
要点: A well-scoped test is a safe and useful test.
第 3

Reconnaissance

Passive reconnaissance gathers information without touching target systems: company websites, job postings revealing technologies, DNS records, certificate transparency logs revealing subdomains, and social media. This is open-source intelligence (OSINT).

Active reconnaissance interacts directly with targets — for example port scanning — and must stay within authorised scope and timing.

  • Passive vs active reconnaissance
  • OSINT sources
  • Certificate transparency and DNS
  • Job postings reveal technology
要点: Good reconnaissance shows what an attacker could learn about you.
第 4

Scanning and enumeration

Port scanning identifies open ports and services. The TCP handshake is SYN, SYN-ACK, ACK; a SYN (half-open) scan does not complete it. Banner grabbing and version detection identify software that may have known vulnerabilities. Enumeration extracts details such as user names, shares, services and configurations.

Attack surface reduction — removing unnecessary services, ports, accounts and software — limits what scanning can find. Default credentials on devices remain a common high-risk finding.

  • Port scanning and the TCP handshake
  • Service and version detection
  • Enumeration
  • Reduce the attack surface
要点: Every exposed service is a potential door.
第 5

Vulnerability analysis and risk

Automated scanners produce false positives and false negatives, so results need validation — for example recognising backported patches that leave version numbers unchanged. CVE identifiers name public vulnerabilities, and CVSS scores severity; network-exploitable flaws needing no authentication or user interaction score higher.

Prioritisation considers severity, exploitability, asset value and business context. Zero-days are unknown to the vendor or unpatched. Threat modelling, such as STRIDE (spoofing, tampering, repudiation, information disclosure, denial of service, elevation of privilege), identifies likely attack paths.

  • Validate scanner output
  • CVE and CVSS
  • Business-context prioritisation
  • Zero-days and threat modelling
要点: Severity scores inform priorities; business context decides them.
第 6

Web application security

The OWASP Top 10 lists critical web risks. SQL injection alters query logic through untrusted input and is prevented with parameterised queries and least-privilege database accounts. XSS runs malicious scripts in users' browsers; defences include context-aware output encoding, input validation and Content Security Policy. CSRF forces authenticated browsers to send unwanted requests; anti-CSRF tokens and SameSite cookies defend against it.

IDOR — changing an ID to view another customer's invoice — is a form of broken access control. SSRF makes servers request unintended locations such as cloud metadata endpoints. Security misconfigurations and vulnerable components are common. SAST analyses source code, DAST tests running applications, and secure development adds requirements, code review, automated testing and training.

  • SQL injection and parameterised queries
  • XSS, CSRF and their defences
  • Broken access control and IDOR
  • SSRF and misconfiguration
  • SAST, DAST and secure development
要点: Never trust input, and always check authorisation.
第 7

Authentication and sessions

Credential stuffing reuses leaked username/password pairs; password spraying tries a few common passwords across many accounts. Defences include MFA, rate limiting, monitoring failed logins and blocking known-breached passwords. Passwords must be stored with salted, slow hashes such as bcrypt, scrypt or Argon2.

Session weaknesses include predictable IDs, sessions that never expire and IDs in URLs. Secure and HttpOnly cookie flags limit exposure.

  • Credential stuffing vs spraying
  • MFA and rate limiting
  • Salted slow hashing
  • Secure session management
要点: Identity is the new perimeter.
第 8

Networks, Active Directory, wireless and cloud

Privilege escalation gains higher permissions — vertically (to administrator) or horizontally (another user's resources) — often via unpatched kernels, misconfigured services or weak permissions. Post-exploitation demonstrates impact within scope, using simulated or minimal data rather than copying real sensitive data. Lateral movement spreads between systems; network segmentation limits it. TLS with certificate validation prevents on-path attacks.

Active Directory controls authentication for many systems; Kerberoasting targets service accounts with weak passwords, countered by long or managed passwords and monitoring. WPA3 uses SAE to resist offline guessing; rogue access points and poorly segmented guest Wi-Fi are common findings. In the cloud shared responsibility model, customers secure configurations, data and identities; public storage buckets are a frequent finding, and provider testing policies must be respected.

  • Privilege escalation and lateral movement
  • Segmentation and TLS
  • Active Directory and service accounts
  • Wireless: WPA3, rogue APs, guest isolation
  • Cloud shared responsibility
要点: Assume breach, and limit how far an attacker can go.
第 9

Social engineering and physical testing

Social engineering exploits trust, urgency and authority through phishing, vishing and tailgating. Authorised phishing simulations measure awareness and improve training without humiliating individuals.

Physical testing needs specific authorisation and a letter testers can present if challenged.

  • Phishing, vishing, tailgating
  • Ethical simulations
  • Physical testing authorisation
  • People are part of the attack surface
要点: Train people, don't shame them.
第 10

Adversary emulation and disclosure

Red teams emulate realistic adversaries over time to test detection and response; blue teams defend; purple teams collaborate to improve detection. MITRE ATT&CK catalogues adversary tactics and techniques.

Responsible disclosure reports vulnerabilities privately and allows time for fixes. Bug bounty programmes reward researchers within published rules. Without a programme, look for a security contact such as security.txt, report privately, avoid further access and never demand payment.

  • Red, blue and purple teams
  • MITRE ATT&CK
  • Coordinated disclosure
  • Bug bounty rules
要点: Disclosure should protect users, not expose them.
第 11

Reporting and remediation

Reports include an executive summary for leaders, scope, methodology, findings with evidence, risk ratings and remediation steps. Each finding describes affected assets, evidence, impact, rating and fixes. Retesting confirms remediation.

Recommendations should strengthen defence in depth, least privilege, patch management, logging and monitoring — for example, when tester activity goes undetected despite alerts, improve triage and response. The goal is reducing business risk, not maximising the number of findings. Ethical hacking helps organisations fix weaknesses before attackers exploit them.

  • Executive summary and technical findings
  • Clear remediation and retesting
  • Defence in depth and least privilege
  • Detection and response improvements
要点: A test is only valuable if it leads to fixes.

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

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

开始免费考试