EXAM QUICK REFERENCE
Section A builds breadth; Section B tests whether you can carry algorithms and security reasoning through to the end. Sixteen chapters separate shared concepts from section-specific solving moves.
Follows the current IPA FE Syllabus v9.2 and Sections A/B; excludes the proposed 2027 format.
Question practice is open. These resources are available without signing in.
QUICK REFERENCE
Showing 6 items
資産・脅威・脆弱性・対策
Separate the protected asset, possible threat, exploitable weakness, and risk-reducing control.
List business assets and security objectives.
Pair threats with their corresponding vulnerabilities.
Verify that the control reduces the stated risk.
Each control must answer which concrete risk it reduces.
権限表
Map users or roles against resources and allowed actions to assess permissions.
Put subjects in rows and resources in columns.
Fill in allowed actions such as read, write, and execute.
Check excessive privilege and separation-of-duties conflicts.
Use least privilege to find both excessive access and missing required access.
ログと時系列
Order accounts, addresses, devices, and events by time to reconstruct what happened.
Normalize time zones and sort timestamps.
Link accounts, IPs, sessions, and device identifiers.
Record facts and inferences separately.
Treat logged events as facts and unsupported claims as inferences.
攻撃経路
Trace an attack through entry, lateral movement, privilege escalation, and objective.
Identify the initial entry point and trust boundary.
Mark lateral movement and privilege escalation.
Match preventive or detective controls to each stage.
Match controls to attack stages instead of choosing one universal measure.
暗号技術の選択
Choose cryptographic techniques from goals such as confidentiality, integrity, authentication, and non-repudiation.
Mark the required security property.
Compare symmetric keys, public keys, hashes, and signatures.
Verify key ownership and verification direction.
Set the security objective before checking key ownership and who can verify.
インシデント対応
Handle incidents through containment, evidence preservation, eradication, recovery, and review.
Contain impact and preserve evidence first.
Eradicate the cause before restoring service.
Review root cause and implement recurrence prevention.
Urgent recovery must not destroy logs and evidence needed for investigation.
