Ethical Hacking Projects for a Beginner Portfolio

Build a beginner ethical hacking portfolio around authorised assessment work you can verify and explain. Start with a clear scope, compare observed behaviour with an expected rule, and document the evidence, remediation proposal and retest status. A small completed assessment gives a reviewer something concrete to inspect.

Nov 22, 2026 - 08:00
3
Ethical Hacking Projects for a Beginner Portfolio
Ethical hacking assessment, verification and reporting with WebAsha branding

Build a beginner ethical hacking portfolio around authorised assessment work you can verify and explain. Start with a clear scope, compare observed behaviour with an expected rule, and document the evidence, remediation proposal and retest status. A small completed assessment gives a reviewer something concrete to inspect.

The four projects below focus on defensive assessment skills. One includes a locally tested Python policy exercise; the other briefs describe work to perform in a permitted lab. None requires testing a public target or collecting real credentials.

Save evidence of the reasoning

  • State the rule or requirement before the check.
  • Record the environment and actual result.
  • Explain the consequence supported by that evidence.
  • Keep proposed fixes separate from verified retests.

Choose a project with a clear assessment question

Four beginner assessment projects
Project Question Portfolio evidence
Permission matrix Does the intended role have only its approved actions? Policy table, test cases, output and limitations.
Synthetic cookie review Which documented cookie attributes are present? Example header, interpretation and context questions.
Vulnerability triage Does a sample finding apply to the stated lab? Evidence comparison, status and review rationale.
Remediation retest Did the approved change produce the intended behaviour? Before/after results, test scope and remaining uncertainty.

Pick the project whose prerequisites you can already explain. For a foundation checklist, use the WebAsha beginner cybersecurity guide. Increase complexity after you can reproduce the first result.

Four assessment stages: scope, compare, validate and report
Suggested workflow for a small authorised assessment project.

Write the scope before collecting evidence

Name the files, identities or lab services you may inspect. Define the permitted checks, expected outcome and point at which you should stop and contact the owner. Use fictional users and synthetic data for the first version.

Store the original task brief with your notes. An instructor’s permission to perform a lab does not automatically grant permission to publish its materials. Ask which parts can appear in a public portfolio and remove confidential assessment content.

OWASP Juice Shop is an intentionally insecure training application. If you use it for a later extension, follow the official setup documentation and keep the environment isolated. The offline project below does not require installing it. [4]

Project 1: check a fictional permission matrix

OWASP recommends least privilege, default denial and permission checks on every request. Use those principles to create a fictional policy before attempting an application-level test. [1]

Give a viewer read access, an editor read/write access and an administrator the actions listed in your task brief. Include a role that does not exist. The purpose is to compare the policy with expected cases, not to build a complete authentication system.

Save the following as check_policy.py. Prerequisite: a local Python 3 interpreter. Run python check_policy.py using your workstation’s Python 3 launcher. It uses synthetic in-memory data, prints results and makes no network request.

Run and explain the policy exercise

permissions = {
    "viewer": {"read"},
    "editor": {"read", "write"},
    "admin": {"read", "write", "delete"},
}

cases = [
    ("viewer", "read", True),
    ("viewer", "delete", False),
    ("editor", "write", True),
    ("unknown", "read", False),
    ("admin", "export", False),
]

for role, action, expected in cases:
    allowed = action in permissions.get(role, set())
    result = "PASS" if allowed == expected else "FAIL"
    decision = "ALLOW" if allowed else "DENY"
    print(f"{role}:{action} {decision} {result}")

Expected output:

viewer:read ALLOW PASS
viewer:delete DENY PASS
editor:write ALLOW PASS
unknown:read DENY PASS
admin:export DENY PASS

The sample was executed locally and the output matched. The unknown role and unlisted action are denied because the lookup does not supply permission for them. The administrator label does not silently grant every possible action.

Acceptance check: add an expected case, explain its intended result and run the exercise again. Temporarily remove the editor’s write permission in your own copy and confirm that the corresponding test reports FAIL. Record that controlled change and restore your baseline.

This checks a dictionary policy only. It does not authenticate a user, enforce a web endpoint or establish resistance to bypasses. A later approved application test must verify the real enforcement location and relevant request paths.

Project 2: review a synthetic cookie configuration

Use a fictional header rather than copying a live session value. MDN documents that Secure restricts a cookie to secure requests, subject to the documented localhost exception, while HttpOnly prevents direct JavaScript access through interfaces such as document.cookie. [2]

Set-Cookie: demo_session=synthetic-value; Secure; HttpOnly; SameSite=Lax; Path=/

Label the example as synthetic. Describe each attribute and note which questions remain: what the application needs, where the cookie is used and how the server manages the session. Do not treat the presence of flags as proof of complete session security.

MDN explains that SameSite affects cookie handling with cross-site requests. Its appropriate setting depends on application behaviour; a static example alone cannot establish whether a production workflow is correct. [2]

Finish with: the example, a short interpretation and a list of application-specific checks you would request. No live cookie, password or session token belongs in the public report.

Project 3: triage a fictional vulnerability finding

Create a small fictional report describing a software issue and a separate lab inventory with product name, version and configuration. Include one finding that fits the inventory and another that lacks enough context to decide.

For each item, state the claim, relevant evidence and review status. Suitable learning statuses include confirmed within the exercise, not applicable to the supplied inventory and insufficient evidence. Explain what would change your conclusion.

A useful triage note does more than repeat a scanner label. It identifies the asset, the applicability question and the next verification step. Use invented identifiers clearly labelled as fictional, or obtain a real advisory from the vendor and preserve its exact scope.

Completion check: a peer can trace your conclusion to the supplied records. You have not claimed a live system is vulnerable or safe based on an incomplete fictional inventory.

Project 4: document an approved remediation retest

Use a disposable local exercise where you can change a simple permission rule. Record the baseline, propose the intended correction and repeat the relevant allowed and denied cases after the change. Keep unrelated files and services outside scope.

Suggested retest record
Record What it should establish
Original observation The behaviour before the approved change.
Expected correction The specific action or boundary that should change.
Changed configuration What you actually modified in the exercise.
Retest cases Allowed and denied behaviour checked after the change.
Actual outcome What the evidence supports and whether more checks are needed.
Limitations Other paths or conditions you did not test.

Use accurate status wording. “Proposed” means the change has not been implemented. “Retested within this lab” describes the checked cases, without asserting that every possible path is secure.

Four parts of a finding: observation, evidence, recommendation and verification
Keep the status of each claim clear when turning lab work into a portfolio report.

Package the work so another person can review it

GitHub’s README guidance includes explaining a project’s purpose and how someone can get started. Put that overview before detailed screenshots or tool output. [3]

Include scope, prerequisites, safe sample inputs, steps and expected results. State what you completed yourself and credit tutorials or assistance. Name the limitation most relevant to the project, such as the policy exercise’s lack of application enforcement.

Keep raw private notes out of the publication package. Test links while signed out, inspect attachments and confirm reuse permissions. The WebAsha beginner portfolio guide offers more documentation ideas.

Review the project before adding it to a resume

Ask someone to follow the instructions with the supplied sample. Record where they needed help and update the README. Then practise explaining the assessment question, your evidence and one failed attempt you corrected.

Describe personal lab work as a project. Do not turn it into an employment claim or imply you tested an organisation that did not authorise the work. For a SOC direction, compare your evidence and handover habits with the SOC analyst skills guide.

Ask WebAsha Technologies about ethical hacking foundation training and supervised project review. Contact WebAsha with your starting skills and the assessment task you want to learn.

Official references

  1. OWASP: Authorization Cheat Sheet
  2. GitHub: About repository README files
  3. OWASP Juice Shop project

Frequently Asked Questions

Choose a small authorised assessment with a clear expected result. A fictional permission matrix is a manageable starting point because you can define rules, run tests and explain limitations without contacting any external system.

No. Use synthetic records, local exercises or explicitly authorised training environments. Public availability does not grant testing permission. Keep the scope and publication conditions with your project notes before collecting or sharing evidence.

It checks whether a small dictionary policy matches the supplied expected cases. It does not authenticate users or enforce a real application. Application-level authorisation requires separate approved tests of the actual enforcement paths.

It checks the behaviour when no role permissions are defined. In this exercise the result is denial. Explain the expected rule before running the case, then record whether the actual outcome matches it.

Use a synthetic example instead. Live session values can expose access or private information. Explain the attributes and context questions without publishing tokens, credentials or personal records from a real application.

They address particular cookie behaviours, not every session risk. Explain what each flag limits and what remains dependent on application design, server-side handling and other controls. Avoid a blanket safety conclusion from a header alone.

State that evidence is insufficient and identify the missing context or test. Keep the original observation separate from the conclusion. A tool label or fictional inventory should not become a confirmed production vulnerability claim.

It compares relevant behaviour before and after an approved change, including allowed and denied cases. Record the actual result and test scope. A recommendation alone is not evidence that a correction was implemented or worked.

Credit the source and follow its reuse terms. Explain what you reproduced, what you changed and which checks you performed. A reviewer should be able to identify your contribution and follow your documented result.

Describe the question, authorised scope, prerequisites, sample input, method, expected result and actual observations. Add limitations, credits and safe reproduction instructions. Inspect every attachment before publishing and confirm that referenced files are present.

There is no universal count. Start with a completed relevant assessment you can explain, then add work that addresses a specific role requirement. Describe your actual contribution and avoid claiming a guaranteed hiring outcome.

Ask a trainer or peer to reproduce your permitted exercise and review its reasoning, evidence and limitations. Use the feedback to improve the report. Share only material you have permission to disclose.

What's Your Reaction?

Like Like 0
Dislike Dislike 0
Love Love 0
Funny Funny 0
Wow Wow 0
Sad Sad 0
Angry Angry 0
Aayushi Sinha

With a passion for staying on the cutting edge of technology trends, I am dedicated to delivering content that not only informs but also inspires. Whether you need in-depth analysis pieces, informative guides, or thought-provoking opinion pieces, I craft content that resonates with tech enthusiasts and professionals alike.