Skip to main content
Certifications GIAC GPEN Home projects Back to certification

Home labs & practical projects

Prioritise findings from an internal training assessment

A project to do with your own tools, with guidance on what to create and capture.

Authorised security lab Suggested time: 2–3 hoursYour own authorised environment
01

What you could create

An authorised lab assessment reveals several weaknesses. The fictional client needs an order of action rather than an undifferentiated list.

Example evidence format
Project evidence map (example)
Prioritised internal assessment reportScope and inputs
Remediation verification planDecisions and reasoning
Evidence record (example)
EvidenceWhat to capture
Prioritised internal assessment reportShow the inputs, scope and decisions behind this record. Priority is explained beyond the scanner’s severity label.
Remediation verification planInclude the evidence supporting your conclusion. The retest checks the underlying condition rather than only rerunning a scan.
02

What you'll need

Authorised security lab

Use findings from a permitted training range and assign fictional business roles to the affected systems. Do not extend testing beyond the range.

Project record

Keep the working files for prioritised internal assessment report and record assumptions as you go.

Current reference material

Use the linked provider resources to verify the features, access terms and version relevant to your project.

Access & cost

Use a deliberately vulnerable local image or a licensed training range. Check the provider’s access terms and current price.

Only test systems you own or are explicitly authorised to assess. Keep targets isolated and use synthetic accounts and data.

03

Suggested milestones

  1. 1

    Plan and investigate

    Validate the evidence and scope for each selected finding.

  2. 2

    Develop your approach

    Rank remediation using exposure, business importance and dependencies.

  3. 3

    Verify and explain

    Design a retest that confirms the fix without collecting unnecessary data.

04

Useful resources

Use these resources to deepen your understanding and check key details.

Turn the project into evidence

Keep your artefacts and reasoning together so you can explain what you did.

A useful starting point

Use findings from a permitted training range and assign fictional business roles to the affected systems. Do not extend testing beyond the range.

What a good result looks like
  • Priority is explained beyond the scanner’s severity label.
  • The retest checks the underlying condition rather than only rerunning a scan.

Finish the project

Revert target snapshots, remove test accounts and artefacts, and store a sanitised report. Do not publish credentials or working attack material.

Independent home-project guidance, not an official vendor lab or a claim of complete exam coverage. Use your own tools and label the work accurately.