Study guide
3.3 International Standards: ISO/IEC 27037, ACPO Principles & ENFSI Guidelines
Computer Hacking Forensic Investigator CHFI 312-49
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Foundations of Digital Forensics & Cybercrime Investigation
1.1 Cybercrime Classifications, Forensic Science Principles & Legal Admissibility 1.2 RFC 3227 Order of Volatility, Live vs. Dead Acquisition & Forensic Readiness 1.3 Indicators of Compromise (IoCs), Cyber Attribution & Threat Intelligence 1.4 AI-Assisted Forensics, GitOps, Automation/Orchestration & Forensics-as-a-Service (FaaS)
2 Chapter 2: Modern Forensic Environments & Emerging Threats
2.1 Fileless Malware, In-Memory Execution & Living-off-the-Land (LotL) 2.2 IoT & Operational Technology (OT/SCADA) Forensic Fundamentals 2.3 Dark Web, Tor Network, Onion Routing & Hidden Services Forensics 2.4 Blockchain Transactions, Cryptocurrency Tracing & Digital Asset Investigations
3 Chapter 3: Legal Frameworks, Search Warrants & Evidence Rules
3.1 Federal Rules of Evidence (FRE 702, 901, 902, 1001-1003) & Daubert/Frye Standards 3.2 Fourth Amendment, Warrant Exceptions, Workplace Search & Consent Protocols 3.3 International Standards: ISO/IEC 27037, ACPO Principles & ENFSI Guidelines 3.4 Cybercrime Statutes, Privacy Compliance, CAN-SPAM & International Cooperation
4 Chapter 4: eDiscovery, Chain of Custody & Professional Ethics
4.1 Electronic Discovery Reference Model (EDRM) & Legal Spoliation Holds 4.2 Chain of Custody Documentation, Evidence Packaging & Tamper-Evident Handling 4.3 Expert Witness Testimony, Report Writing Standards & EC-Council Code of Ethics
5 Chapter 5: Storage Architecture, Boot Sequences & Media Forensics
5.1 Storage Media Architecture: Sectors, Clusters, RAM/File Slack & Unallocated Space 5.2 Partition Tables & Boot Structures: MBR, GPT, VBR, BIOS vs. UEFI Secure Boot 5.3 RAID Reconstruction (RAID 0, 1, 5, 6, 10) & SSD Forensic Challenges (TRIM, Wear Leveling)
6 Chapter 6: Windows File Systems: NTFS & FAT
6.1 NTFS Architecture: Master File Table ($MFT) Record Structure & Attribute Headers 6.2 NTFS Artifacts: Alternate Data Streams (ADS), Volume Shadow Copies (VSS) & $LogFile 6.3 FAT12/16/32 and exFAT Architecture, Directory Entries & File Deletion Mechanics
7 Chapter 7: Non-Windows File Systems & File Signatures
7.1 Linux File Systems: ext2/ext3/ext4 Inode Architecture, Superblocks & Journaling Forensics 7.2 macOS File Systems: HFS+ and Apple File System (APFS) Architecture & Snapshots 7.3 File Signatures, Magic Bytes, Hex Headers/Footers & File Carving Techniques
8 Chapter 8: Investigation Lifecycle, Lab Setup & First Response
8.1 Forensic Laboratory Accreditation: ISO/IEC 17025 Standards & Hardware/Software Controls 8.2 First Responder Duties: Crime Scene Containment, Electronic Triage & Volatile Triage 8.3 Physical Evidence Packaging, Anti-Static/Faraday Protection & Transport Security
9 Chapter 9: Forensic Acquisition & Verification Methodology
9.1 Hardware and Software Write-Blockers: Operational Validation & Bridge Verification 9.2 Bit-Stream Disk Imaging, Physical vs. Logical vs. Targeted Acquisition Methodology 9.3 Forensic Image Formats (RAW/DD, E01, AFF) & Cryptographic Hashing Verification (MD5, SHA-256)
10 Chapter 10: Anti-Forensics Techniques & Countermeasures
10.1 Steganography Detection: Spatial/Frequency Domain Steganalysis & Hidden Carrier Extraction 10.2 Timestomping Countermeasures: Comparing $STANDARD_INFORMATION vs $FILE_NAME Timestamps 10.3 Secure Wiping, Degaussing, File Shredding Countermeasures & Residual Artifact Recovery
11 Chapter 11: Windows Operating System Forensics
11.1 Windows Registry Forensics: SYSTEM, SOFTWARE, SAM & NTUSER.DAT Hive Analysis 11.2 Execution Artifacts: Prefetch (.pf), Shimcache (AppCompatCache), Amcache.hve & UserAssist 11.3 User Activity Artifacts: ShellBags, LNK Shortcut Files, Jump Lists & Recycle Bin ($I/$R) 11.4 Windows Event Log Forensics: Security Audit IDs (4624, 4625, 4688, 4720, 7045) & EVTX Parsing
12 Chapter 12: Memory Forensics & Malware Analysis
12.1 Volatile Memory Acquisition: RAM Capture, Crash Dumps, Hiberfil.sys & Pagefile.sys 12.2 Memory Analysis with Volatility 3: pslist, pstree, malfind, netscan & Vadinfo 12.3 Static Malware Triage: Strings, PE Headers, Import Tables, Hashes & YARA Rule Matching 12.4 Dynamic Malware Analysis: Sandboxing, Process Monitor (Procmon), Regshot & Network Callouts 12.5 .NET Managed Malware Analysis & the GOOTLOADER Fileless Infection Chain
13 Chapter 13: Network, Web Application & Email Forensics
13.1 Network Forensics: PCAP Analysis, Protocol Dissection, Snort/Suricata & Flow Analysis 13.2 Web Server Forensics: Apache/IIS Access Logs, SQL Injection, XSS & Web Shell Detection 13.3 Email Forensics: RFC 5322 Headers, Authentication (SPF, DKIM, DMARC) & Mbox/PST Extraction 13.4 SIEM Event Correlation, Cross-Source Timeline Analysis & Super-Timeline Construction 13.5 Investigating Directory Traversal, Command Injection, Parameter Tampering, XXE, Cookie Poisoning & Brute Force 13.6 Network Device & Service Log Forensics: Firewall, IDS, Honeypot, Router, DHCP, Switch, VPN, DNS & SSH 13.7 Wireless Network Forensics: Rogue APs, Evil Twins, MAC Spoofing, Deauthentication & Jamming
14 Chapter 14: Mobile, Cloud & IoT Forensics
14.1 Mobile Device Forensics: Manual, Logical, File System & Physical Extraction (Android/iOS) 14.2 Mobile Artifact Analysis: Call Logs, SMS/Chat SQLite Databases, Location Data & Plists 14.3 Cloud Forensics: AWS CloudTrail, Azure Activity Logs & Multi-Tenant Evidence Collection 14.4 IoT Forensics: UART/JTAG Physical Interfaces, Firmware Extraction & Sensor Telemetry
15 Chapter 15: Commercial & Open-Source Forensic Suites
15.1 Commercial Forensic Platforms: EnCase Forensic, FTK (Forensic Toolkit) & FTK Imager 15.2 Open-Source Forensic Platforms: Autopsy, The Sleuth Kit (TSK) & SIFT/CAINE Workstations 15.3 Specialized DFIR Utilities: Eric Zimmerman Tools (EZ Tools) & Sysinternals Forensic Suite
16 Chapter 16: Analysis Toolkits, Python Scripting & Tool Validation
16.1 Reverse Engineering & Password Cracking: Ghidra, IDA Pro, Hashcat & John the Ripper 16.2 Python for Digital Forensics: Parsing Raw Artifacts, Custom Scapy Scripts & Evidence Automation 16.3 Forensic Tool Testing & Validation: NIST CFTT Methodology, ISO/IEC 17025 Standards & Daubert Compliance
17 Chapter 17: Database Forensics & Web Application Firewalls
17.1 MySQL Forensics: Internal Architecture, Data Directory, Information Schema & Utility Programs 17.2 SQL Server Forensics: SSMS, ApexSQL, SQLCMD Transaction-Log Collection, Plan Cache & Trace Files 17.3 Web Application Firewall (WAF) Architecture, Audit Logs, Benefits & Limitations
18 Chapter 18: Social, Virtualized, Multimedia & Browser Investigations
18.1 Social Media, Social Engineering, Insider Threat & Identity Theft Forensics 18.2 Virtualization, Container & Microservices Forensics, Bluetooth and Electron Chat Applications 18.3 Multimedia Forensics: Image, Audio & Video Authentication, EXIF, PRNU and Deepfake Detection 18.4 Browser Artifact Recovery, Private Browsing, USB Enumeration, Partition Recovery & Packer Unpacking Tools
3.3 International Standards: ISO/IEC 27037, ACPO Principles & ENFSI Guidelines
Key Takeaways Explain This Topic AI
ISO/IEC 27037 establishes an international four-phase methodology for digital evidence handling: Identification, Collection, Acquisition, and Preservation (ICAP).
The standard clearly defines two operational roles: Digital Evidence First Responders (DEFR) who manage on-scene physical containment, and Digital Evidence Specialists (DES) who perform advanced technical acquisitions and live forensics.
ACPO Principle 1 establishes the baseline rule that no action should alter digital evidence, while Principle 2 creates a strict exception requiring demonstrated competence and written justification when live original data must be accessed.
ACPO Principle 3 mandates complete audit trails enabling independent third-party reproducibility, and ENFSI guidelines require formal method validation and ISO/IEC 17025 laboratory accreditation for cross-border evidentiary defensibility.
Last updated: September 2026
3.3 International Standards: ISO/IEC 27037, ACPO Principles & ENFSI Guidelines
Quick Answer: International digital forensics relies on standardized frameworks to ensure evidence remains admissible across global jurisdictions. ISO/IEC 27037 governs initial evidence handling across four phases: Identification, Collection, Acquisition, and Preservation (ICAP) , delineating responsibilities between Digital Evidence First Responders (DEFR) and Digital Evidence Specialists (DES) . The UK ACPO Good Practice Guide defines four core principles: Principle 1 (no action should alter data), Principle 2 (exceptional access requires competence and justification), Principle 3 (comprehensive audit trails enabling independent reproducibility), and Principle 4 (officer in charge ensures compliance). In Europe, ENFSI enforces rigorous quality assurance, proficiency testing, method validation, and ISO/IEC 17025 laboratory accreditation.
The Imperative of International Standardization in Digital Forensics
Modern cybercrime is inherently transnational. A threat actor situated in Eastern Europe can orchestrate a ransomware campaign compromising cloud servers in North America using command-and-control (C2) infrastructure routing through Western Europe. When digital evidence is obtained across national borders, prosecutors and defense counsel rely on Mutual Legal Assistance Treaties (MLATs) , letters rogatory, and the Budapest Convention on Cybercrime (Council of Europe ETS No. 185).
For digital evidence acquired in one nation to be admitted into court in another, investigators must demonstrate adherence to globally recognized, standardized forensic methodologies. Without harmonized standards, variations in evidence acquisition, forensic imaging, and chain of custody documentation provide opposing counsel with grounds to challenge reliability, leading to evidence suppression.
ISO/IEC 27037: The International Standard for Digital Evidence Handling
Published jointly by the International Organization for Standardization (ISO) and the International Electrotechnical Commission (IEC), ISO/IEC 27037:2012 provides comprehensive 'Guidelines for identification, collection, acquisition, and preservation of digital evidence.'
The standard governs the initial handling of Potential Digital Evidence (PDE) —defined as any digital data that can be used to establish that a crime has been committed or can provide a link between an incident and its perpetrator or victim. ISO/IEC 27037 applies across all standard digital devices, including computer systems, network peripherals, storage media, mobile phones, automotive infotainment units, and embedded IoT systems. +-----------------------------------------------------------------------------------------+
- | ISO/IEC 27037 FOUR CORE PROCESSES (ICAP) |
- +-----------------------------------------------------------------------------------------+
- | 1. IDENTIFICATION -> Recognizing, distinguishing, and cataloging potential evidence |
- | 2. COLLECTION -> Physically packaging, labeling, and securing devices from scene |
- | 3. ACQUISITION -> Generating bit-stream duplicates / logical extractions with hashes |
- | 4. PRESERVATION -> Maintaining continuous physical & cryptographic integrity |
- +-----------------------------------------------------------------------------------------+
- The Four ICAP Phases
Identification: The initial process of locating, identifying, and distinguishing potential sources of digital evidence from surrounding irrelevant hardware. The investigator must document the physical scene, cable configurations, network connections, system power states (powered on, powered off, sleeping, or suspended), and peripheral devices.
Collection: The physical process of seizing and securing hardware devices from the scene. Devices are photographed in situ, safely disconnected, labeled with unique evidence tracking identifiers, and packaged into anti-static bags or RF-shielded Faraday enclosures before transport.
Acquisition: The technical process of creating an exact digital copy of potential evidence. Acquisition involves generating bit-stream physical disk images (sector-by-sector duplicates) or targeted logical extractions using write-blocking mechanisms. Cryptographic hash algorithms (SHA-256 or MD5) must be computed simultaneously to document baseline integrity.
Preservation: The ongoing process of maintaining the physical condition, environmental stability, and cryptographic integrity of both original physical media and acquired digital copies throughout storage, transport, laboratory analysis, and post-trial archiving.
Operational Roles: DEFR vs. DES
ISO/IEC 27037 formally establishes two distinct operational roles to ensure tasks are executed only by personnel with appropriate technical qualifications:
Functional Role Definition & Qualifications Permitted Operational Scope
Digital Evidence First Responder (DEFR) Trained law enforcement officer, incident responder, or corporate security staff who arrives first on scene. Trained in foundational evidence protocols. - Identifying physical computing equipment.; - Documenting and photographing the scene.; - Packaging and physical labeling of devices.; - Applying write-protection locks and Faraday bags.; - Transporting evidence to the laboratory.
Digital Evidence Specialist (DES) Certified digital forensic practitioner possessing advanced scientific training, specialized hardware/software tools, and deep OS/file system knowledge. - Live volatile memory (RAM) acquisition.; - Triage of running, encrypted file systems.; - Complex mobile chip-off and JTAG acquisitions.; - RAID reconstruction and cloud infrastructure captures.; - Full forensic analysis and expert witness testimony.
Three Fundamental Evidence Principles under ISO/IEC 27037
Relevance: The acquisition process must target potential evidence that directly impacts the specific incident under investigation.
Reliability: The tools, hardware bridges, and acquisition workflows used must yield consistent, accurate, and scientifically verifiable results.
Sufficiency: The volume, scope, and depth of evidence collected must be sufficient to support factual findings without leaving critical investigative gaps.
The ACPO Good Practice Guide for Digital Evidence: Four Core Principles
Developed in the United Kingdom by the Association of Chief Police Officers (ACPO) , the Good Practice Guide for Digital Evidence is recognized worldwide as the gold standard for procedural defensibility. The ACPO guide articulates Four Core Principles that every forensic investigator must know verbatim for the CHFI examination: +-----------------------------------------------------------------------------------------+
- | FOUR CORE ACPO PRINCIPLES |
- +-----------------------------------------------------------------------------------------+
- | Principle 1: Data Integrity -> No action should change data used in court |
- | Principle 2: Competence & Reason -> Live access requires demonstrated competence |
- | Principle 3: Audit Trail -> 100% repeatable by independent third party |
- | Principle 4: Officer in Charge -> Lead investigator ensures statutory compliance |
- +-----------------------------------------------------------------------------------------+
- Detailed Analysis of ACPO Principles
- Principle 1: No Action Should Change Data
"No action taken by law enforcement agencies, persons employed by those agencies, or their agents should change data which may subsequently be relied upon in court."
This is the bedrock rule of digital forensics. When acquiring or examining storage media, investigators must use hardware write-blockers (e.g., Tableau, WiebeTech) or software write-blocking drivers to guarantee that not a single byte, sector, or timestamp on the suspect drive is altered. Analysis is performed strictly on forensic copies, leaving the original evidence untouched.
Principle 2: Competence and Justification for Accessing Original Data
"In circumstances where a person finds it necessary to access original data, that person must be competent to do so and be able to explain the relevance and the implications of their actions."
Principle 2 establishes the narrow, vital exception to Principle 1: Live Forensics . In modern computing, full-disk encryption (Microsoft BitLocker, Apple FileVault, Linux LUKS) is ubiquitous. If an investigator unplugs a running, encrypted system, the cryptographic keys stored in volatile RAM are lost instantly, rendering the disk permanently inaccessible. Under Principle 2, a qualified forensic specialist may interact with a running machine to capture RAM and dump mounted volumes, provided they are technically competent and meticulously document every command and its memory footprint.
Principle 3: Comprehensive Audit Trail and Independent Reproducibility
"An audit trail or other record of all processes applied to digital evidence should be created and preserved. An independent third party should be able to examine those processes and achieve the same result."
Principle 3 codifies the scientific requirement of repeatability and reproducibility . The examiner must maintain detailed contemporaneous notes: exact hardware serial numbers, firmware revisions, forensic software tool versions, terminal commands, arguments, and intermediate hash calculations. If an independent defense expert follows the recorded steps on the verified forensic duplicate, they must reach the exact same results.
Principle 4: Responsibility of the Officer in Charge
"The officer in charge of the investigation has overall responsibility for ensuring that the law and these principles are adhered to."
Principle 4 establishes management accountability. The senior investigator, forensic lab supervisor, or officer in charge retains ultimate legal responsibility for ensuring that all participating staff, first responders, and specialized contractors adhere to statutory search rules and evidence handling standards.
ENFSI Guidelines: Quality Management, Laboratory Accreditation & Method Validation
The European Network of Forensic Science Institutes (ENFSI) coordinates forensic science practices across Europe. Its Forensic Information Technology Working Group (FITWG) produces the Guidelines for Best Practice in the Forensic Examination of Digital Technology .
ENFSI aligns digital forensics with formal laboratory accreditation under ISO/IEC 17025 ( General requirements for the competence of testing and calibration laboratories ): +-----------------------------------------------------------------------------------------+
- | ENFSI QUALITY ASSURANCE PILLARS (ISO/IEC 17025) |
- +-----------------------------------------------------------------------------------------+
- | Standard Operating Procedures (SOPs) -> Detailed, repeatable step-by-step lab manuals |
- | Method Validation -> Testing tools against NIST CFTT ground-truth |
- | Proficiency Testing -> Blind external challenges (e.g., CTS tests) |
- | Peer Review -> Technical audit of reports prior to release |
- +-----------------------------------------------------------------------------------------+
- 1. Standard Operating Procedures (SOPs)
Every forensic operation—media sanitization, dead-box acquisition, RAM capture, registry extraction, and mobile decoding—must be governed by formal, version-controlled SOPs. Deviations from an SOP must be documented, justified, and approved by the laboratory director.
2. Method Validation and Ground-Truth Testing
Under ENFSI guidelines, a forensic laboratory cannot simply deploy a software utility because it was released by a commercial vendor. The lab must conduct method validation to verify that the tool performs accurately and reliably under real-world operating conditions.
Laboratories utilize standardized reference data sets, such as the NIST Computer Forensic Reference Data Sets (CFReDS) .
Tools are tested against known ground-truth disk images containing deliberate anomalies (e.g., deleted files, bad sectors, slack space artifacts, Alternate Data Streams).
3. Proficiency Testing and Collaborative Exercises
To maintain ISO/IEC 17025 accreditation, forensic examiners must undergo regular blind proficiency testing administered by external evaluation bodies (such as Collaborative Testing Services [CTS]). In a blind test, an examiner is provided an unknown disk image with planted artifacts and must correctly identify, reconstruct, and report all findings without prior knowledge of the answer key.
4. Technical Peer Review
Before an official forensic report or witness statement is signed and submitted to a court or prosecution team, ENFSI mandates a comprehensive peer review . A second qualified digital forensics specialist independently verifies the examiner's notes, checks tool logs, recalculates hashes, and confirms that the analytical conclusions are fully supported by the underlying technical data.
Comparative Framework Matrix
Dimension ISO/IEC 27037 ACPO Good Practice Guide ENFSI Guidelines (FITWG)
Geographic Scope Global International Standard (ISO/IEC). United Kingdom origins; adopted across Commonwealth & globally. European Union & partner forensic institutes.
Core Lifecycle Model ICAP: Identification, Collection, Acquisition, Preservation. Four Core Evidentiary Principles. Four Quality Assurance Pillars under ISO/IEC 17025.
Primary Target Initial on-scene first response and acquisition. Investigative conduct, live access, and auditability. Laboratory quality management, tool validation, and peer review.
Defined Personnel Roles DEFR (First Responder) vs. DES (Specialist). Officer in Charge vs. Competent Examiner. Quality Manager, Technical Lead, Case Examiner, Peer Reviewer.
Live Triage Rule Directs DEFR to request DES when live complexity is met. Principle 2: Permitted only with competence and justification. Governed by validated live-triage SOPs and audit logging.
Auditability Standard Continuous chain of custody documentation. Principle 3: 100% third-party independent reproducibility. ISO 17025 audit trail, peer review, and test record retention.
Practical Implementation: Commands, Scripts, and Forensic Integrity Workflows
To comply with ISO/IEC 27037 and ACPO Principle 1 and Principle 3, examiners utilize hardware write-blockers and validated command-line utilities that generate automated audit trails and multi-hash verifications.
Verifying Hardware Write-Blocker Status in Linux
Prior to connecting suspect media to an analysis workstation, the examiner must confirm that the host kernel recognizes the storage bridge as read-only: # Check block device read-only flag (1 = Read-Only, 0 = Read-Write)
- blockdev --getro /dev/sdb
- 1
- # Query device parameters using hdparm
- sudo hdparm -r /dev/sdb
/dev/sdb:
- readonly = 1 (on)
- Bit-Stream Acquisition with Simultaneous Multi-Hashing via dcfldd
The open-source enhanced acquisition utility dcfldd (developed by the DoD Computer Forensics Laboratory) provides cryptographic hashing, status tracking, and automated audit logging satisfying ACPO Principle 3: # Forensically image suspect drive /dev/sdb to raw format with dual hashing
- sudo dcfldd if=/dev/sdb of=/evidence/case_2026_09/drive_sdb.raw \
- hash=sha256,md5 \
- sha256log=/evidence/case_2026_09/sha256.log \
- md5log=/evidence/case_2026_09/md5.log \
- statusinterval=1024000
- Verifying Acquired Image Integrity
Once acquisition concludes, the examiner recalculates the hash of the target image file to verify match: # Recalculate SHA-256 hash of the resulting raw image file
- sha256sum /evidence/case_2026_09/drive_sdb.raw
- # Output matches the hash generated during initial acquisition
- e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 /evidence/case_2026_09/drive_sdb.raw
- Real-World Forensic Scenario & Exam Tips
Scenario: A patrol officer responding to an unauthorized computer access incident finds an enterprise database server powered on. The screen displays an active terminal connection copying customer credit card tables to an off-shore IP address. The officer, having no digital forensics training, immediately presses the power button to shut down the server.
Result: The officer violated ISO/IEC 27037 role boundaries and ACPO Principle 1 and 2. Because the server was powered down abruptly, all volatile network connection states (active sockets), running process trees, injected memory modules, and encryption keys in RAM were lost. As a DEFR, the officer should have isolated the machine from the network (by pulling the Ethernet cable) and contacted a Digital Evidence Specialist (DES) to perform live acquisition.
CHFI Exam Tips on International Standards
Memorize the ACPO Principles by number:
Principle 1: No action should change data.
Principle 2: Exceptional access requires competence and justification.
Principle 3: Audit trail enabling third-party reproducibility.
Principle 4: Officer in charge ensures compliance.
Know the ISO/IEC 27037 acronym ICAP: I dentification, C ollection, A cquisition, P reservation.
Distinguish DEFR vs. DES: DEFR handles physical containment and packaging; DES handles live memory, advanced imaging, and laboratory analysis.
Link ENFSI to ISO/IEC 17025: ENFSI mandates laboratory accreditation under ISO/IEC 17025, which focuses on calibration, method validation, and proficiency testing.