Start with evidence, not a list of tools
One well-documented security lab is more useful than ten screenshots of tools. The projects below are designed to produce evidence a hiring manager can inspect: a defined scope, a diagram, configuration, tests, findings and a short explanation of what you would improve next.
This guide is part of the first IT job series. Beginners should start with a home-network audit, firewall lab or secure web application. Malware analysis and penetration testing belong in an isolated lab and must only involve systems and samples you are authorised to examine.
For each project, keep the scope and threat model, an architecture diagram, the commands or configuration, before-and-after test results, useful screenshots or logs, and a brief retrospective. Those artefacts prove more than a certificate or a list of product names.
Home Network Security Audit
Audit a home network you own. Draw the device and trust-boundary map, inventory exposed services, review router and Wi-Fi settings, check patch levels, and record each finding with a practical mitigation. Redact public IP addresses, passwords, device serial numbers and family information before adding evidence to a public portfolio.
Here are some ideas of what your cyber security audit can address:
- Wi-Fi Network Security
- Firewall
- Network Devices
- Software Updates
- Antivirus Software
- Secure Configurations
- IoT Devices
- VPNs
- Phishing Awareness
- Data Backup
- Two-factor authentication (2FA)
- Password Management
Make sure to document your planning, findings, and mitigations.
Malware Analysis
Use a purpose-built, isolated analysis lab and a legally obtained training sample. Record hashes, static findings, observed behaviour, indicators of compromise and containment advice. Do not run live malware on your normal computer or home network; a safe simulated incident is still a valid beginner project.
Secure Website Development
Build a small web application with authentication, input validation, secure secret handling and useful security headers. Add a threat model and automated tests for the controls you implemented. The portfolio value comes from explaining the design decisions and showing the tests fail when a control is removed.
Understanding HTML, CSS, and JavaScript can significantly improve your cybersecurity skills. Here’s how:
- Identifying Malicious Code: Knowledge of these languages can help you identify potentially malicious code embedded in a website. Examples of malicious code could be JavaScript code designed to download malware onto a user’s computer or a script intended to carry out Cross-Site Scripting (XSS) attacks.
- Understanding Web Applications: Many cybersecurity attacks target web applications. Understanding how these applications are built (often with HTML, CSS, and JavaScript) can help you identify potential vulnerabilities and protect against attacks.
- Penetration Testing: Penetration testers (or ethical hackers) must understand how websites and web applications work to find vulnerabilities. Knowledge of HTML, CSS, and JavaScript is useful for this.
- Secure Coding Practices: Understanding these languages can help you implement safe coding practices. For example, properly knowing how to sanitize user input in JavaScript can prevent many attacks.
- Cross-Site Scripting (XSS) and Cross-Site Request Forgery (CSRF) Attacks: These attacks exploit a website’s JavaScript vulnerabilities. Understanding JavaScript can help you protect against these attacks.
- Website Defacement: Cybersecurity professionals must understand how websites are built to protect against and recover from website defacement attacks.
- Phishing Attacks: Phishing attacks often involve fake websites that trick users into entering their login credentials. Understanding HTML and CSS can help you identify these fake websites.
- Debugging and Inspecting Web Elements: Knowledge of HTML, CSS, and JavaScript allows you to use browser tools to inspect web elements, debug issues, and understand the structure and behavior of a website or web application.
In Cyber Security, it is essential to comprehend the various web technologies. This understanding will enable you to identify and mitigate potential threats effectively. Again, document all the problems or interesting struggles you had along the way.
Incident Response Plan
Write an incident response plan for a clearly defined fictional organisation, then run a tabletop exercise against it. Include severity criteria, decision owners, communications, evidence handling, containment steps and a post-incident review. Record the gaps the exercise exposed and revise the plan.
Security Awareness Training Program
Create a short awareness module for one audience and one risk, such as invoice fraud for accounts staff. Include the learning objective, a realistic example, a knowledge check and a way to measure whether the training changed behaviour. Avoid collecting real credentials or sending surprise phishing simulations without approval.
Penetration Testing
Test an intentionally vulnerable lab application or a system you own and are explicitly authorised to assess. Define the rules of engagement first, keep a time-stamped activity log, and finish with a report that separates evidence, risk, remediation and retest results. A clean report is often more persuasive than a long list of scanner findings.
Firewall Configuration
Build a small segmented lab and write the minimum firewall rules required for its traffic flows. Test an allowed connection, a blocked connection and logging for both. Include the network diagram, rule rationale and rollback plan so another person could review the design.
Cryptography Project
Use a maintained cryptographic library to protect a small application or data flow; do not invent a production cipher. Document the threat model, key generation, storage, rotation and failure handling. Tests should prove that authorised access works and common misuse is rejected.
Security Policy Development
Write one usable security policy for a defined fictional organisation, then map each requirement to an owner and a piece of evidence. A focused access-control, backup or vulnerability-management policy is more credible than a generic document that tries to cover everything.
IoT Security Project
Place an IoT device in a separate lab network, document its normal connections and restrict unnecessary traffic. Review update behaviour, default credentials, data collection and recovery options. Publish the network design and findings without exposing the device to the public internet.
Which project should you build first?
Start with the project you can complete and explain safely. For most beginners, that is a home-network audit, firewall lab or secure web application. Finish it, ask someone to review the evidence, then improve the same project before starting a harder one.
As with any portfolio, clear documentation is critical. Include a detailed description of each project, the technologies used, how you tested it and the challenges you faced. Then use the entry-level IT resume and portfolio guide to show cybersecurity projects without overstating lab work as production experience. Only test systems you own or are explicitly authorised to assess.
I really appreciate the thoughts shared in this blog post.
The article describes ten challenging cybersecurity project ideas that can be used to enhance a person’s portfolio. These projects include a home network security audit, malware analysis, secure website development, incident response plan, security awareness training program, penetration testing, firewall configuration, cryptography project, security policy development, and IoT security project. Clear documentation is key to the success of these projects.
Wayne
Thanks Wayne! Documentation does encompass a large part of cyber security even if it is boring.
Thanks