CHFI case studies
CHFI · Put your knowledge to work in context.
This independent study page provides practice for CHFI. Its editorial learning areas include Digital evidence, acquisition and bounded forensic conclusions; Filesystem, memory, network and timeline evidence; Identity, access and cryptographic protection; Security operations, monitoring and response; Cyber-risk identification and analysis; Continuity, backup and technical recovery. The CHFI case studies are 5 cases and about 1,039 words.
1A matching hash does not identify the human actor
A fictional authorized investigation preserves a storage image and records matching integrity hashes for the acquired and working copies. A supplied log contains a source network address and an account name, but the environment also has shared accounts, an intermediary gateway and uncertain clock alignment.
170 words, under 1 min2SaaS access after a role change
A fictional organization uses a managed collaboration service for internal planning documents. The provider maintains the application and underlying servers, while the organization configures users, groups and sharing settings.
221 words, about 1 min3An incident review with an action that can be checked
A fictional delivery team restores service after a release encounters an undocumented database dependency. The initial meeting ends with the statement that the engineer should be more careful, but no owner, test or review date is recorded.
219 words, about 1 min4A control comparison with explicit effectiveness and uncertainty
A fictional organization estimates the value exposed by one defined incident scenario at five hundred thousand currency units and the fraction lost in one successful incident at forty percent. Its classroom model estimates an annualized incident rate of one half, and the exercise asks for expected annual loss rather than a prediction that exactly half an incident occurs each year.
206 words, about 1 min5A recovery target does not prescribe one universal architecture
A fictional order service has a recovery-point objective of fifteen minutes and a recovery-time objective of four hours. A tested option creates consistent recovery points every ten minutes and restores the service in three hours after the declared recovery procedure begins.
223 words, about 1 min