Home labs & practical projects
Review a historical firewall rulebase
A project to do with your own tools, with guidance on what to create and capture.
For existing holders and historical learning. Check the current credential before starting exam preparation.
What you could create
An existing PCNSA holder inherits a firewall rulebase with broad rules and unclear ownership. The task is to improve its documentation and reviewability.
| Evidence | What to capture |
|---|---|
| Rulebase review worksheet | Show the inputs, scope and decisions behind this record. A low hit count is not treated as sufficient reason to delete a rule. |
| Staged cleanup and verification proposal | Include the evidence supporting your conclusion. The review preserves necessary traffic and distinguishes historical credential context. |
What you'll need
Document, spreadsheet or diagram tool
Create six fictional rules with source, destination, application intent and hit counts. Include an unused rule and a wide exception; use current documentation for product details.
Project record
Keep the working files for rulebase review worksheet 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
No paid platform is needed for the written version. Use a document, spreadsheet or diagram tool you already have.
The organisation and records are fictional. Write down assumptions; do not substitute confidential employer information.
Suggested milestones
- 1
Plan and investigate
Map each rule to a business purpose and owner.
- 2
Develop your approach
Identify overly broad matches and potential rule-order effects.
- 3
Verify and explain
Propose a staged cleanup with logging, validation and rollback.
Useful resources
Use these resources to deepen your understanding and check key details.
A useful starting point
Create six fictional rules with source, destination, application intent and hit counts. Include an unused rule and a wide exception; use current documentation for product details.
What a good result looks like
- A low hit count is not treated as sufficient reason to delete a rule.
- The review preserves necessary traffic and distinguishes historical credential context.
Finish the project
Keep the decision record and note unanswered questions. A written design is not evidence that a technical control has been tested.
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.