Hands-on emulator lab · 6–10 min
Find the most useful security fix to make next — Security Hub CSPM
Import a harmless training finding and find it in a security findings list.
These actions use an isolated AWS Emulator. It stores API state locally; it does not create paid cloud resources or run the full hosted AWS service.
Your goal
Import a harmless training finding and find it in a security findings list.
Why this matters
Teams need a consistent format to review findings from different tools. You will import a low-severity training record and retrieve it by ID. No actual incident or compliance result is fabricated.
Words you will use
CSPM means cloud security posture management. A control checks a security practice. A finding reports a result. Posture describes how well settings match intended safeguards.
How to proceed
Start a fresh emulator, read each numbered step, and enter the practice settings shown. Run the action, inspect its API receipt, then continue. Finish lab checks the emulator state again before saving your progress.
1. Enable the practice hub
Enable Security Hub without default standards. This gives the emulator a place to store findings. It does not scan real resources or certify that a system is secure.
2. Import a low-severity training finding
Save a clearly labeled practice finding using the standard finding format. The title, severity, and affected resource make it easier for a team to understand and sort an issue.
3. Find the imported record
Query by the exact finding ID and inspect its title and severity. The check uses the stored finding. A training finding should never be mistaken for an actual incident.
Practice, then check your understanding
Perform the actions yourself and inspect the returned state. Errors keep your settings so you can retry. Starting another lab clears the previous live environment. Earned XP is kept, and signed-in achievements sync to your account. Replay does not award duplicate XP.
Read the official AWS documentation for service behavior and production details.