{"id":3702,"date":"2026-10-29T10:31:39","date_gmt":"2026-10-29T07:31:39","guid":{"rendered":"https:\/\/niteducation.com\/resources\/?p=3702"},"modified":"2026-10-29T10:31:42","modified_gmt":"2026-10-29T07:31:42","slug":"cybersecurity-projects-for-beginners","status":"publish","type":"post","link":"https:\/\/niteducation.com\/resources\/cybersecurity-projects-for-beginners\/","title":{"rendered":"Cybersecurity Projects for Beginners: 8 Step-by-Step Labs | NIT"},"content":{"rendered":"\n<!--\nNewton Institute of Technology \u2014 Article 208\nMaster Stylesheet v6.3 Premium production build \u2014 28 October 2026\nWordPress supplies the page's only semantic H1; the article hero uses .nit-hero__title.\nLoad the locked nit-articles-master-v6.3.css once at site level.\nNo article-specific CSS, inline styles, scripts, Base64 images or new component classes are used in this body.\nCanonical production URL: https:\/\/niteducation.com\/resources\/cybersecurity-projects-for-beginners\/\nPrimary search intent: help a complete beginner choose and complete practical cybersecurity projects that produce evidence of real skills.\nCannibalization boundary: Cybersecurity Career owns jobs and employer expectations; Entry-Level Cybersecurity owns first-role selection; Can You Learn Cybersecurity Without Coding owns coding requirements; Analyst vs Ethical Hacker owns role comparison; What a Cybersecurity Analyst Does owns day-to-day work; Online Cybersecurity Training owns full lab\/laptop readiness; Cybersecurity Course owns programme\/admissions. Article 208 owns beginner project execution, evidence, retesting and portfolio presentation.\nNo article image is required: v6.3 cards, workflows, tables and code-window components communicate the practical content without an additional asset.\n-->\n<article aria-labelledby=\"nit-article-title\" class=\"nit-article nit-article--cyber nit-article--software nit-article--pathway-guide nit-article--c-plus-degree\" itemscope itemtype=\"https:\/\/schema.org\/Article\">\n<meta itemprop=\"datePublished\" content=\"2026-10-28\">\n<meta itemprop=\"dateModified\" content=\"2026-10-28\">\n<meta itemprop=\"inLanguage\" content=\"en-KE\">\n<meta itemprop=\"author\" content=\"Newton Institute of Technology Editorial Team\">\n\n<div aria-labelledby=\"nit-article-title\" class=\"nit-pg-hero\">\n  <div>\n    <p class=\"nit-pg-kicker\">Cybersecurity Beginner Projects<\/p>\n    <p class=\"nit-hero__title\" id=\"nit-article-title\" itemprop=\"headline\">Cybersecurity Projects for Beginners:<br>8 Step-by-Step Labs to Build Real Skills<\/p>\n    <p class=\"nit-pg-hero__line\">understand <i>\u2192<\/i> observe <i>\u2192<\/i> investigate <i>\u2192<\/i> improve <i>\u2192<\/i> retest<\/p>\n    <p class=\"nit-pg-hero__summary\" itemprop=\"description\">Build practical cybersecurity skills with eight controlled projects you can complete, explain and turn into portfolio evidence\u2014even if you are starting with one laptop and little or no coding experience.<\/p>\n    <div class=\"nit-pg-hero__actions\">\n      <a class=\"nit-pg-button nit-pg-button--gold\" href=\"#projects-at-a-glance\">Choose a project<\/a>\n      <a class=\"nit-pg-button nit-pg-button--outline\" href=\"#project-score\">Score your work<\/a>\n    <\/div>\n  <\/div>\n  <div aria-label=\"Beginner cybersecurity project pathway\" class=\"nit-deg-hero__art\">\n    <p>Turn a lab exercise into evidence you can explain.<\/p>\n    <div aria-hidden=\"true\" class=\"nit-deg-orbit\">\n      <strong>8<\/strong>\n      <span class=\"nit-deg-orbit__chip nit-deg-orbit__chip--tech\">MAP<\/span>\n      <span class=\"nit-deg-orbit__chip nit-deg-orbit__chip--health\">LOGS<\/span>\n      <span class=\"nit-deg-orbit__chip nit-deg-orbit__chip--business\">CODE<\/span>\n      <span class=\"nit-deg-orbit__chip nit-deg-orbit__chip--stem\">TEST<\/span>\n    <\/div>\n    <div class=\"nit-deg-hero__note\">\n      <span>Project standard<\/span>\n      <strong>Evidence + reasoning + retest<\/strong>\n      <small>Do not stop when a command runs. Explain the result and verify what changed.<\/small>\n    <\/div>\n  <\/div>\n  <div aria-label=\"Article summary\" class=\"nit-pg-hero__meta\">\n    <p><span>Projects<\/span>8 core labs<\/p>\n    <p><span>Coding<\/span>7 can start without it<\/p>\n    <p><span>Best for<\/span>Students + beginners<\/p>\n    <p><span>Last reviewed<\/span>28 October 2026<\/p>\n  <\/div>\n<\/div>\n\n<div class=\"nit-article__body\">\n<section aria-labelledby=\"quick-answer-title\" class=\"nit-quick-answer\" id=\"quick-answer\">\n  <div class=\"nit-quick-answer__head\">\n    <span aria-hidden=\"true\" class=\"nit-quick-answer__mark\">A<\/span>\n    <div><p class=\"nit-quick-answer__label\">Quick answer<\/p><p class=\"nit-quick-answer__kicker\" id=\"quick-answer-title\">What cybersecurity project should a beginner start with?<\/p><\/div>\n  <\/div>\n  <div class=\"nit-quick-answer__body\">\n    <p class=\"nit-quick-answer__text\"><strong>Start by mapping a small environment you own, then inspect traffic and harden one test computer.<\/strong> These projects teach you what exists, how systems communicate, what a normal configuration looks like and how to verify a security change before you move into web-security testing or larger tools.<\/p>\n    <ul aria-label=\"Beginner project facts\" class=\"nit-quick-answer__signals\">\n      <li>One laptop can be enough<\/li>\n      <li>Most projects need no coding<\/li>\n      <li>Use only authorised systems<\/li>\n      <li>Save evidence, not just screenshots<\/li>\n      <li>Retest every important change<\/li>\n    <\/ul>\n  <\/div>\n<\/section>\n\n<nav aria-label=\"Article contents\" class=\"nit-toc\">\n  <h2>Contents<\/h2>\n  <ol>\n    <li><a href=\"#projects-at-a-glance\">8 projects at a glance<\/a><\/li>\n    <li><a href=\"#project-standard\">What makes a real project?<\/a><\/li>\n    <li><a href=\"#safe-practice\">Safe and authorised practice<\/a><\/li>\n    <li><a href=\"#project-1\">1. Map your environment<\/a><\/li>\n    <li><a href=\"#project-2\">2. Analyse traffic<\/a><\/li>\n    <li><a href=\"#project-3\">3. Harden a computer<\/a><\/li>\n    <li><a href=\"#project-4\">4. Investigate phishing<\/a><\/li>\n    <li><a href=\"#project-5\">5. Build an integrity checker<\/a><\/li>\n    <li><a href=\"#project-6\">6. Investigate Windows logins<\/a><\/li>\n    <li><a href=\"#project-7\">7. Test a vulnerable app<\/a><\/li>\n    <li><a href=\"#project-8\">8. Complete an assessment<\/a><\/li>\n    <li><a href=\"#portfolio\">Portfolio guidance<\/a><\/li>\n    <li><a href=\"#project-score\">20-point project score<\/a><\/li>\n    <li><a href=\"#faq\">FAQs<\/a><\/li>\n  <\/ol>\n<\/nav>\n\n<section class=\"nit-section-panel\" id=\"projects-at-a-glance\">\n  <h2>8 cybersecurity projects for beginners at a glance<\/h2>\n  <p>Choose a project you can finish and explain. Project count matters less than whether you can show your scope, evidence, reasoning and verification.<\/p>\n  <div class=\"nit-curriculum-grid\">\n    <article class=\"nit-curriculum-card\"><span class=\"nit-curriculum-card__period\">Project 1 \u00b7 No coding<\/span><h3>Map your practice environment<\/h3><p>Identify devices, interfaces, addresses and expected services. <strong>Output:<\/strong> network diagram + asset register.<\/p><\/article>\n    <article class=\"nit-curriculum-card\"><span class=\"nit-curriculum-card__period\">Project 2 \u00b7 No coding<\/span><h3>Analyse traffic with Wireshark<\/h3><p>Observe DNS, TCP, TLS or QUIC traffic from your own computer. <strong>Output:<\/strong> annotated traffic report.<\/p><\/article>\n    <article class=\"nit-curriculum-card\"><span class=\"nit-curriculum-card__period\">Project 3 \u00b7 No coding<\/span><h3>Harden a test computer<\/h3><p>Record a baseline, change one justified setting and verify it. <strong>Output:<\/strong> before\/after checklist.<\/p><\/article>\n    <article class=\"nit-curriculum-card\"><span class=\"nit-curriculum-card__period\">Project 4 \u00b7 No coding<\/span><h3>Investigate a training email<\/h3><p>Use sender, link, language and header evidence to reach a verdict. <strong>Output:<\/strong> incident note.<\/p><\/article>\n    <article class=\"nit-curriculum-card\"><span class=\"nit-curriculum-card__period\">Project 5 \u00b7 Basic Python<\/span><h3>Build a file-integrity checker<\/h3><p>Create and compare SHA-256 baselines. <strong>Output:<\/strong> working script + test results.<\/p><\/article>\n    <article class=\"nit-curriculum-card\"><span class=\"nit-curriculum-card__period\">Project 6 \u00b7 No coding<\/span><h3>Investigate Windows logins<\/h3><p>Compare failed and successful authentication events. <strong>Output:<\/strong> event timeline + analyst note.<\/p><\/article>\n    <article class=\"nit-curriculum-card\"><span class=\"nit-curriculum-card__period\">Project 7 \u00b7 Controlled lab<\/span><h3>Assess an intentionally vulnerable app<\/h3><p>Document one weakness in OWASP Juice Shop. <strong>Output:<\/strong> finding + remediation + retest plan.<\/p><\/article>\n    <article class=\"nit-curriculum-card\"><span class=\"nit-curriculum-card__period\">Project 8 \u00b7 Capstone<\/span><h3>Complete a security assessment<\/h3><p>Combine assets, configuration, logs and one authorised finding. <strong>Output:<\/strong> complete assessment report.<\/p><\/article>\n  <\/div>\n<\/section>\n\n<section id=\"project-standard\">\n  <h2>What turns a tutorial into a real cybersecurity project?<\/h2>\n  <p>A tutorial tells you what to click or type. A project makes you decide what the evidence means. NIST&#8217;s NICE Framework describes cybersecurity work and capability using work roles, competency areas, and Task, Knowledge and Skill statements; the current Components v2.2.0 were released on 28 April 2026. <a href=\"#source-1\" aria-label=\"Reference 1\">[1]<\/a> NIST&#8217;s technical security-testing guidance also treats assessment as a process that moves from planning and testing into analysis and mitigation. <a href=\"#source-2\" aria-label=\"Reference 2\">[2]<\/a><\/p>\n  <div class=\"nit-pg-reasons\" aria-label=\"Six-part cybersecurity project standard\">\n<div><span>01<\/span><h3>Scope<\/h3><p>State exactly what system you own or are authorised to test.<\/p><\/div>\n<div><span>02<\/span><h3>Objective<\/h3><p>Write the security question before opening the tool.<\/p><\/div>\n<div><span>03<\/span><h3>Evidence<\/h3><p>Capture only the logs, settings, packets, code or screenshots needed to support the result.<\/p><\/div>\n<div><span>04<\/span><h3>Interpretation<\/h3><p>Explain what the evidence supports\u2014and what it does not prove.<\/p><\/div>\n<div><span>05<\/span><h3>Action<\/h3><p>Make or recommend a proportionate improvement.<\/p><\/div>\n<div><span>06<\/span><h3>Verification<\/h3><p>Repeat the relevant check and record whether the change actually worked.<\/p><\/div>\n<\/div>\n  <div class=\"nit-callout nit-callout--success\"><p class=\"nit-callout__title\">The rule to remember<\/p><p><strong>Do something you can explain and verify.<\/strong> A command that runs successfully is the beginning of the learning, not the end.<\/p><\/div>\n<\/section>\n\n<section class=\"nit-section-panel\" id=\"safe-practice\">\n  <h2>Before you begin: practise only where you have authority<\/h2>\n  <p>Use your own computer, your own network, your own virtual machines, an intentionally vulnerable training application, or another system for which you have explicit permission. Kenya&#8217;s Computer Misuse and Cybercrimes Act addresses unauthorised access and interference; its definition of unauthorised access turns on whether the person is entitled to control access or has consent from someone who is. <a href=\"#source-3\" aria-label=\"Reference 3\">[3]<\/a><\/p>\n  <p>Nmap&#8217;s official legal guidance recommends obtaining written authorisation before scanning networks you do not own or control. <a href=\"#source-4\" aria-label=\"Reference 4\">[4]<\/a><\/p>\n  <div class=\"nit-callout nit-callout--warning\"><p class=\"nit-callout__title\">Simple learner boundary<\/p><p><strong>Own it, isolate it or have permission to test it.<\/strong> Do not make a school, business, neighbour or random public website your practice target.<\/p><\/div>\n<\/section>\n\n<section id=\"one-laptop\">\n  <h2>You can start with one ordinary laptop<\/h2>\n  <div class=\"nit-module-grid\">\n    <article class=\"nit-module-card\"><div class=\"nit-module-card__head\"><span class=\"nit-module-card__number\">01<\/span><h3>Low-demand route<\/h3><\/div><p>Projects 1, 3, 4 and 6 can be completed using normal operating-system tools plus documentation.<\/p><p class=\"nit-module-card__outcome\">Best when hardware is limited.<\/p><\/article>\n    <article class=\"nit-module-card\"><div class=\"nit-module-card__head\"><span class=\"nit-module-card__number\">02<\/span><h3>Network-analysis route<\/h3><\/div><p>Add Wireshark for Project 2 and learn to interpret your own traffic before attempting heavier security platforms.<\/p><p class=\"nit-module-card__outcome\">Best for networking and SOC interest.<\/p><\/article>\n    <article class=\"nit-module-card\"><div class=\"nit-module-card__head\"><span class=\"nit-module-card__number\">03<\/span><h3>Coding route<\/h3><\/div><p>Add Python for Project 5. The program is intentionally small so the security idea stays more important than the amount of code.<\/p><p class=\"nit-module-card__outcome\">Best for automation interest.<\/p><\/article>\n    <article class=\"nit-module-card\"><div class=\"nit-module-card__head\"><span class=\"nit-module-card__number\">04<\/span><h3>Virtual-lab route<\/h3><\/div><p>When your computer can comfortably run virtual machines or containers, add the local Juice Shop lab and the capstone assessment.<\/p><p class=\"nit-module-card__outcome\">Best after the foundations are clear.<\/p><\/article>\n  <\/div>\n  <p>NIT&#8217;s current Cybersecurity programme similarly connects systems, networking, Linux, authorised testing, monitoring, incident response, scripting and technical reporting rather than treating cybersecurity as a single hacking tool. <a href=\"#source-13\" aria-label=\"Reference 13\">[13]<\/a><\/p>\n<\/section>\n\n<section class=\"nit-section-panel\" id=\"project-1\">\n  <h2>Project 1: Map your own cybersecurity practice environment<\/h2>\n  <p><strong>Difficulty:<\/strong> Beginner \u00b7 <strong>Coding:<\/strong> No \u00b7 <strong>Typical session:<\/strong> 45\u201390 minutes \u00b7 <strong>Output:<\/strong> network diagram + asset register<\/p>\n  <p>The first question is not \u201cWhich hacking tool should I use?\u201d It is <strong>\u201cWhat am I protecting?\u201d<\/strong> CIS Control 1 focuses on inventorying enterprise assets so systems that need monitoring and protection can be identified; your beginner version applies the same idea to a tiny environment you own. <a href=\"#source-5\" aria-label=\"Reference 5\">[5]<\/a><\/p>\n  <div class=\"nit-pg-reasons\" aria-label=\"Project 1 workflow\">\n<div><span>01<\/span><h3>List your assets<\/h3><p>Start with your laptop, router, phone and\u2014if you have one\u2014a virtual machine.<\/p><\/div>\n<div><span>02<\/span><h3>Find local network information<\/h3><p>On Windows use <code>ipconfig<\/code>; on Linux use <code>ip addr<\/code>. Identify the active interface, local address and gateway.<\/p><\/div>\n<div><span>03<\/span><h3>Draw the environment<\/h3><p>A simple Internet \u2192 router \u2192 laptop \u2192 virtual machine diagram is enough.<\/p><\/div>\n<div><span>04<\/span><h3>Examine your own host<\/h3><p>If Nmap is installed, <code>nmap 127.0.0.1<\/code> introduces ports and listening services on your own machine.<\/p><\/div>\n<div><span>05<\/span><h3>Add an authorised second host<\/h3><p>If you created a VM, scan its private lab address. Do not confuse localhost scanning with mapping a whole network.<\/p><\/div>\n<div><span>06<\/span><h3>Turn ports into questions<\/h3><p>Ask what service owns the port, why it is running, whether it is expected and whether it needs to be exposed.<\/p><\/div>\n<div><span>07<\/span><h3>Update the asset register<\/h3><p>Record important observations and the decision to keep, investigate or change each one.<\/p><\/div>\n<div><span>08<\/span><h3>Explain the result<\/h3><p>Write one paragraph describing what you learnt rather than attaching unexplained scanner output.<\/p><\/div>\n<\/div>\n  <div class=\"nit-table-wrap\"><table class=\"nit-table\"><thead><tr><th scope=\"col\">Asset<\/th><th scope=\"col\">Purpose<\/th><th scope=\"col\">Observation<\/th><th scope=\"col\">Decision<\/th><\/tr><\/thead><tbody><tr><td>Windows laptop<\/td><td>Main practice computer<\/td><td>Local service listening<\/td><td>Identify service before changing it<\/td><\/tr><tr><td>Linux VM<\/td><td>Training system<\/td><td>SSH available<\/td><td>Keep because the lab requires it<\/td><\/tr><tr><td>Test share<\/td><td>Old exercise<\/td><td>No longer required<\/td><td>Investigate and remove safely<\/td><\/tr><\/tbody><\/table><\/div><p class=\"nit-table-note\">On a small screen, swipe the table sideways to see every column.<\/p>\n  <div class=\"nit-callout nit-callout--info\"><p class=\"nit-callout__title\">Real-life example: a school computer laboratory<\/p><p>A school with 15 student PCs, an instructor PC, a printer and a router still begins with the same questions: Which devices exist? Which are authorised? What is each used for? Which systems should communicate? Your four-device lab practises the same reasoning at a safer scale.<\/p><\/div>\n  <div class=\"nit-action-strip\"><p><strong>Completion test:<\/strong> You can explain which systems exist, how they connect, what at least one observed service does, and why you decided to keep, investigate or change it.<\/p><\/div>\n<\/section>\n\n<section id=\"project-2\">\n  <h2>Project 2: Analyse your own network traffic with Wireshark<\/h2>\n  <p><strong>Difficulty:<\/strong> Beginner \u00b7 <strong>Coding:<\/strong> No \u00b7 <strong>Typical session:<\/strong> 60\u201390 minutes \u00b7 <strong>Output:<\/strong> annotated packet-analysis report<\/p>\n  <p>Wireshark provides display filters and tools for analysing endpoints, conversations and protocols. <a href=\"#source-6\" aria-label=\"Reference 6\">[6]<\/a> Keep this project limited to traffic generated by your own computer or another authorised lab system.<\/p>\n  <div class=\"nit-pg-reasons\" aria-label=\"Project 2 Wireshark workflow\">\n<div><span>01<\/span><h3>Reduce background noise<\/h3><p>Close applications you do not need, choose your active Wi-Fi or Ethernet interface and begin a short capture.<\/p><\/div>\n<div><span>02<\/span><h3>Generate one simple activity<\/h3><p>Open a normal website yourself, then stop the capture.<\/p><\/div>\n<div><span>03<\/span><h3>Find DNS<\/h3><p>Apply the <code>dns<\/code> display filter. Identify a query, who sent it, who answered and what address was returned.<\/p><\/div>\n<div><span>04<\/span><h3>Find TCP<\/h3><p>Apply <code>tcp<\/code>. Choose one conversation and identify source, destination and ports.<\/p><\/div>\n<div><span>05<\/span><h3>Look for TLS<\/h3><p>Apply <code>tls<\/code>. If the browser used HTTPS over TCP, you may see TLS-related traffic.<\/p><\/div>\n<div><span>06<\/span><h3>Check QUIC when needed<\/h3><p>Modern browsers may use QUIC\/HTTP\/3. If the expected TCP\/TLS pattern is missing, try the official <code>quic<\/code> display filter instead. <a href=\"#source-6\" aria-label=\"Reference 6\">[6]<\/a><\/p><\/div>\n<div><span>07<\/span><h3>Build a protocol table<\/h3><p>Record only what you actually observed. Do not invent TLS, TCP or QUIC evidence because a tutorial said it should appear.<\/p><\/div>\n<div><span>08<\/span><h3>Explain one conversation<\/h3><p>Describe who communicated, which protocol appeared and what the traffic was doing in ordinary language.<\/p><\/div>\n<\/div>\n  <div class=\"nit-callout nit-callout--success\"><p class=\"nit-callout__title\">A useful troubleshooting lesson<\/p><p>If your capture shows QUIC where you expected TCP\/TLS, the project has not failed. Your job is to investigate why the evidence differs from your expectation.<\/p><\/div>\n  <div class=\"nit-table-wrap\"><table class=\"nit-table\"><thead><tr><th scope=\"col\">Protocol<\/th><th scope=\"col\">What you might observe<\/th><th scope=\"col\">What it helps accomplish<\/th><\/tr><\/thead><tbody><tr><td>DNS<\/td><td>Name query and response<\/td><td>Find an address<\/td><\/tr><tr><td>TCP<\/td><td>Connection between endpoints<\/td><td>Reliable transport<\/td><\/tr><tr><td>TLS<\/td><td>Encrypted session traffic<\/td><td>Protect application data<\/td><\/tr><tr><td>QUIC<\/td><td>Encrypted UDP-based transport<\/td><td>May carry modern HTTP\/3 traffic<\/td><\/tr><\/tbody><\/table><\/div><p class=\"nit-table-note\">On a small screen, swipe the table sideways to see every column.<\/p>\n  <div class=\"nit-action-strip\"><p><strong>Completion test:<\/strong> Identify one source, one destination and one protocol, explain the communication, and describe one thing that surprised you.<\/p><\/div>\n<\/section>\n\n<section class=\"nit-section-panel\" id=\"project-3\">\n  <h2>Project 3: Harden a Windows or Linux test computer<\/h2>\n  <p><strong>Difficulty:<\/strong> Beginner \u00b7 <strong>Coding:<\/strong> No \u00b7 <strong>Typical session:<\/strong> 60\u2013120 minutes \u00b7 <strong>Output:<\/strong> before\/after hardening report<\/p>\n  <p>Secure configuration and account management are recognised defensive practices in CIS Controls v8.1. <a href=\"#source-5\" aria-label=\"Reference 5\">[5]<\/a> Your project should make one justified change at a time so you can tell what caused the result.<\/p>\n  <div class=\"nit-pg-reasons\" aria-label=\"Project 3 hardening workflow\">\n<div><span>01<\/span><h3>Record the baseline<\/h3><p>Before changing anything, record update status, accounts, administrator privileges, firewall state, sharing, remote access and relevant services.<\/p><\/div>\n<div><span>02<\/span><h3>Review accounts<\/h3><p>Identify which accounts you recognise and which hold administrator privileges. Investigate unfamiliar accounts before deleting them.<\/p><\/div>\n<div><span>03<\/span><h3>Check updates<\/h3><p>Record whether security or operating-system updates are pending.<\/p><\/div>\n<div><span>04<\/span><h3>Check the firewall<\/h3><p>Confirm it is enabled and understand an allow rule before removing it.<\/p><\/div>\n<div><span>05<\/span><h3>Review sharing and remote access<\/h3><p>Look for shares, remote-access settings or old services that the test computer no longer needs.<\/p><\/div>\n<div><span>06<\/span><h3>Choose one improvement<\/h3><p>For example, disable an old test share only after confirming it is unnecessary.<\/p><\/div>\n<div><span>07<\/span><h3>Retest<\/h3><p>Try the same access method again and record whether the exposure is gone.<\/p><\/div>\n<div><span>08<\/span><h3>Check normal use<\/h3><p>A security change that needlessly breaks required functionality is not automatically a good change.<\/p><\/div>\n<\/div>\n  <div class=\"nit-table-wrap\"><table class=\"nit-table\"><thead><tr><th scope=\"col\">Check<\/th><th scope=\"col\">Before<\/th><th scope=\"col\">Action<\/th><th scope=\"col\">Verification<\/th><\/tr><\/thead><tbody><tr><td>Firewall<\/td><td>Enabled<\/td><td>No change<\/td><td>Still enabled<\/td><\/tr><tr><td>Test share<\/td><td>Accessible<\/td><td>Disabled<\/td><td>No longer accessible<\/td><\/tr><tr><td>Updates<\/td><td>Pending<\/td><td>Installed<\/td><td>System current<\/td><\/tr><\/tbody><\/table><\/div><p class=\"nit-table-note\">On a small screen, swipe the table sideways to see every column.<\/p>\n  <div class=\"nit-callout nit-callout--info\"><p class=\"nit-callout__title\">Real-life example: a small office<\/p><p>An old employee account, unnecessary file share and pending updates are not proof that a computer has been attacked. They are conditions worth assessing. A good security practitioner separates evidence from assumption.<\/p><\/div>\n  <div class=\"nit-action-strip\"><p><strong>Completion test:<\/strong> Show at least one complete chain: before \u2192 finding \u2192 reason \u2192 action \u2192 verification.<\/p><\/div>\n<\/section>\n\n<section id=\"project-4\">\n  <h2>Project 4: Investigate a suspicious training email safely<\/h2>\n  <p><strong>Difficulty:<\/strong> Beginner \u00b7 <strong>Coding:<\/strong> No \u00b7 <strong>Typical session:<\/strong> 45\u201360 minutes \u00b7 <strong>Output:<\/strong> one-page incident note<\/p>\n  <p>Use a synthetic email, an instructor-provided message or another safe training sample. CISA&#8217;s phishing guidance highlights clues such as suspicious sender information, urgent or emotionally manipulative wording, unexpected attachments and misleading links. <a href=\"#source-7\" aria-label=\"Reference 7\">[7]<\/a><\/p>\n  <div class=\"nit-pg-reasons\" aria-label=\"Project 4 phishing-analysis workflow\">\n<div><span>01<\/span><h3>Identify the requested action<\/h3><p>Finish the sentence: \u201cThe sender wants the recipient to ___.\u201d This reveals the social-engineering objective.<\/p><\/div>\n<div><span>02<\/span><h3>Compare name and address<\/h3><p>A display name such as \u201cSchool Accounts Office\u201d does not prove the email came from that organisation.<\/p><\/div>\n<div><span>03<\/span><h3>Look for pressure<\/h3><p>Record urgency, threats, account-closure warnings, unexpected rewards or unusual payment requests.<\/p><\/div>\n<div><span>04<\/span><h3>Inspect links safely<\/h3><p>Where your mail client exposes the destination without opening it, compare the real destination with the claimed organisation.<\/p><\/div>\n<div><span>05<\/span><h3>Examine available headers<\/h3><p>Look for From, Reply-To, Return-Path, Received and authentication information where available.<\/p><\/div>\n<div><span>06<\/span><h3>Reach a verdict<\/h3><p>Choose likely legitimate, suspicious\u2014verify independently, or likely phishing. Then explain the evidence behind your decision.<\/p><\/div>\n<\/div>\n  <div class=\"nit-callout nit-callout--warning\"><p class=\"nit-callout__title\">Do not create a second problem<\/p><p>Do not open an unknown attachment to make the project more interesting, and do not publish a real person&#8217;s email address, private message contents, authentication data or an active malicious URL.<\/p><\/div>\n  <div class=\"nit-action-strip\"><p><strong>Completion test:<\/strong> Another reader can understand why you reached your verdict without trusting your conclusion blindly.<\/p><\/div>\n<\/section>\n\n<section class=\"nit-section-panel\" id=\"project-5\">\n  <h2>Project 5: Build a file-integrity checker with Python<\/h2>\n  <p><strong>Difficulty:<\/strong> Beginner\u2013intermediate \u00b7 <strong>Coding:<\/strong> Basic Python \u00b7 <strong>Typical session:<\/strong> 60\u201390 minutes \u00b7 <strong>Output:<\/strong> working script + test results<\/p>\n  <p>Python&#8217;s <code>hashlib<\/code> module provides SHA-256 and other hash functions. <a href=\"#source-8\" aria-label=\"Reference 8\">[8]<\/a> Here you will create a baseline digest, deliberately change a harmless file, then compare the current digest with the stored baseline.<\/p>\n  <div class=\"nit-pg-reasons\" aria-label=\"Project 5 file-integrity workflow\">\n<div><span>01<\/span><h3>Create a harmless file<\/h3><p>Create <code>important.txt<\/code> containing \u201cStudent project &#8211; original version\u201d. Do not use real confidential information.<\/p><\/div>\n<div><span>02<\/span><h3>Create the program<\/h3><p>Use SHA-256 to calculate the file digest and save it as the baseline on the first run.<\/p><\/div>\n<div><span>03<\/span><h3>Verify the unchanged file<\/h3><p>Run the program again without modifying the file. It should report that the current digest matches the baseline.<\/p><\/div>\n<div><span>04<\/span><h3>Change one word<\/h3><p>Edit the test file, run the program again and confirm that the digest comparison now reports a change.<\/p><\/div>\n<div><span>05<\/span><h3>Interpret carefully<\/h3><p>A changed digest shows that the contents differ. It does not tell you who changed the file, why, when or whether the change was malicious.<\/p><\/div>\n<div><span>06<\/span><h3>Identify the trust limitation<\/h3><p>The baseline file is part of the trust problem. If both the target and baseline can be altered, the simple design becomes weaker.<\/p><\/div>\n<\/div>\n  <div class=\"nit-code-window\" aria-label=\"Python SHA-256 file-integrity checker\">\n<div class=\"nit-code-window__bar\"><span class=\"nit-code-window__dot\"><\/span><span class=\"nit-code-window__dot\"><\/span><span class=\"nit-code-window__dot\"><\/span><span class=\"nit-code-window__file\">integrity_check.py<\/span><\/div>\n<div class=\"nit-code-window__body\">\n<span class=\"nit-code-line\"><span class=\"nit-code-keyword\">from<\/span> pathlib <span class=\"nit-code-keyword\">import<\/span> Path<\/span>\n<span class=\"nit-code-line\"><span class=\"nit-code-keyword\">import<\/span> hashlib<\/span>\n<span class=\"nit-code-line\"><\/span>\n<span class=\"nit-code-line\"><span class=\"nit-code-name\">target<\/span> = Path(<span class=\"nit-code-string\">&#8220;important.txt&#8221;<\/span>)<\/span>\n<span class=\"nit-code-line\"><span class=\"nit-code-name\">baseline<\/span> = Path(<span class=\"nit-code-string\">&#8220;important.sha256&#8221;<\/span>)<\/span>\n<span class=\"nit-code-line\"><\/span>\n<span class=\"nit-code-line\"><span class=\"nit-code-name\">digest<\/span> = hashlib.sha256(target.read_bytes()).hexdigest()<\/span>\n<span class=\"nit-code-line\"><\/span>\n<span class=\"nit-code-line\"><span class=\"nit-code-keyword\">if<\/span> <span class=\"nit-code-keyword\">not<\/span> baseline.exists():<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;baseline.write_text(digest)<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;<span class=\"nit-code-keyword\">print<\/span>(<span class=\"nit-code-string\">&#8220;Baseline created&#8221;<\/span>)<\/span>\n<span class=\"nit-code-line\"><span class=\"nit-code-keyword\">elif<\/span> baseline.read_text().strip() == digest:<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;<span class=\"nit-code-keyword\">print<\/span>(<span class=\"nit-code-string\">&#8220;UNCHANGED&#8221;<\/span>)<\/span>\n<span class=\"nit-code-line\"><span class=\"nit-code-keyword\">else<\/span>:<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;<span class=\"nit-code-keyword\">print<\/span>(<span class=\"nit-code-string\">&#8220;CHANGED&#8221;<\/span>)<\/span>\n<\/div>\n<\/div>\n  <div class=\"nit-callout nit-callout--info\"><p class=\"nit-callout__title\">What this project does not prove<\/p><p>Do not write \u201cPython detected a hacker.\u201d A defensible statement is: <strong>\u201cThe current SHA-256 digest differs from the stored baseline, showing that the file contents have changed.\u201d<\/strong><\/p><\/div>\n  <div class=\"nit-action-strip\"><p><strong>Completion test:<\/strong> Your program correctly distinguishes an unchanged file from a deliberately modified file, and you can explain what that result does and does not prove.<\/p><\/div>\n<\/section>\n\n<section id=\"project-6\">\n  <h2>Project 6: Investigate failed Windows logins like a junior analyst<\/h2>\n  <p><strong>Difficulty:<\/strong> Beginner \u00b7 <strong>Coding:<\/strong> No \u00b7 <strong>Typical session:<\/strong> 45\u201390 minutes \u00b7 <strong>Output:<\/strong> event timeline + analyst note<\/p>\n  <p>Microsoft documents Security Event ID <strong>4625<\/strong> for failed logons and Event ID <strong>4624<\/strong> for successful logons. Event 4625 can include the account, failure information, logon type, workstation and network information where applicable. <a href=\"#source-9\" aria-label=\"Reference 9\">[9]<\/a> <a href=\"#source-10\" aria-label=\"Reference 10\">[10]<\/a><\/p>\n  <div class=\"nit-pg-reasons\" aria-label=\"Project 6 Windows log workflow\">\n<div><span>01<\/span><h3>Define the experiment<\/h3><p>On your own Windows test machine, record the computer, test account, current time and planned action.<\/p><\/div>\n<div><span>02<\/span><h3>Generate one controlled failure<\/h3><p>Enter an incorrect password once or twice. Do not repeatedly lock out an important account.<\/p><\/div>\n<div><span>03<\/span><h3>Sign in successfully<\/h3><p>Use the correct credentials so you have success and failure evidence to compare.<\/p><\/div>\n<div><span>04<\/span><h3>Open the Security log<\/h3><p>In Event Viewer, locate the 4625 failure and 4624 success near your recorded timestamps.<\/p><\/div>\n<div><span>05<\/span><h3>Compare the fields<\/h3><p>Review account, failure reason, logon type, workstation and source network address where applicable.<\/p><\/div>\n<div><span>06<\/span><h3>Build a timeline<\/h3><p>Place the events in time order rather than saving one isolated screenshot.<\/p><\/div>\n<div><span>07<\/span><h3>Make an analyst decision<\/h3><p>Two controlled failures do not automatically mean an attack. Context changes the interpretation.<\/p><\/div>\n<div><span>08<\/span><h3>Write a four-part note<\/h3><p>Observation \u2192 evidence \u2192 assessment \u2192 decision.<\/p><\/div>\n<\/div>\n  <div class=\"nit-table-wrap\"><table class=\"nit-table\"><thead><tr><th scope=\"col\">Time<\/th><th scope=\"col\">Event<\/th><th scope=\"col\">Result<\/th><th scope=\"col\">Interpretation<\/th><\/tr><\/thead><tbody><tr><td>10:03<\/td><td>4625<\/td><td>Failure<\/td><td>Controlled wrong password<\/td><\/tr><tr><td>10:04<\/td><td>4625<\/td><td>Failure<\/td><td>Second controlled attempt<\/td><\/tr><tr><td>10:05<\/td><td>4624<\/td><td>Success<\/td><td>Correct credentials<\/td><\/tr><\/tbody><\/table><\/div><p class=\"nit-table-note\">On a small screen, swipe the table sideways to see every column.<\/p>\n  <div class=\"nit-callout nit-callout--info\"><p class=\"nit-callout__title\">If the expected event is missing<\/p><p>Do not invent evidence. Confirm you are looking at the Security log on the machine where the attempt occurred, check the timestamp and investigate whether relevant auditing is enabled. An unexpected result is part of troubleshooting.<\/p><\/div>\n  <div class=\"nit-action-strip\"><p><strong>Completion test:<\/strong> Explain what happened, where Windows recorded it, what the relevant fields mean, and why the controlled activity did or did not require escalation.<\/p><\/div>\n<\/section>\n\n<section class=\"nit-section-panel\" id=\"project-7\">\n  <h2>Project 7: Assess an intentionally vulnerable web application<\/h2>\n  <p><strong>Difficulty:<\/strong> Beginner\u2013intermediate \u00b7 <strong>Coding:<\/strong> Not required initially \u00b7 <strong>Time:<\/strong> Several focused sessions \u00b7 <strong>Output:<\/strong> one documented security finding<\/p>\n  <p>OWASP Juice Shop is deliberately insecure and designed for security training. It includes vulnerabilities from the OWASP Top Ten and can be run locally using several methods, including Docker. <a href=\"#source-11\" aria-label=\"Reference 11\">[11]<\/a><\/p>\n  <div class=\"nit-pg-reasons\" aria-label=\"Project 7 authorised web-security workflow\">\n<div><span>01<\/span><h3>Run a local training target<\/h3><p>Use an official local Juice Shop setup. Keep your test inside the intentionally vulnerable environment. OWASP&#8217;s Web Security Testing Guide also emphasises knowing the test scope and what information is being gathered. <a href=\"#source-12\" aria-label=\"Reference 12\">[12]<\/a><\/p><\/div>\n<div><span>02<\/span><h3>Understand normal behaviour<\/h3><p>Explore login, products, search, basket and account features before testing anything.<\/p><\/div>\n<div><span>03<\/span><h3>Write the scope<\/h3><p>State that the local Juice Shop instance is in scope and public websites are out of scope.<\/p><\/div>\n<div><span>04<\/span><h3>Choose one beginner challenge<\/h3><p>One finding you understand is better than many challenge completions you cannot explain.<\/p><\/div>\n<div><span>05<\/span><h3>Describe expected behaviour<\/h3><p>Write what a normal user should be able to do, then record what happened instead.<\/p><\/div>\n<div><span>06<\/span><h3>Document evidence<\/h3><p>Record title, location, evidence, security impact and recommendation.<\/p><\/div>\n<div><span>07<\/span><h3>Explain it without jargon first<\/h3><p>Describe the security failure in normal language before attaching the technical label.<\/p><\/div>\n<div><span>08<\/span><h3>Create a retest plan<\/h3><p>Write the exact check you would repeat after a developer says the issue is fixed.<\/p><\/div>\n<\/div>\n  <div class=\"nit-code-window\" aria-label=\"OWASP Juice Shop local Docker setup\">\n<div class=\"nit-code-window__bar\"><span class=\"nit-code-window__dot\"><\/span><span class=\"nit-code-window__dot\"><\/span><span class=\"nit-code-window__dot\"><\/span><span class=\"nit-code-window__file\">terminal<\/span><\/div>\n<div class=\"nit-code-window__body\">\n<span class=\"nit-code-line\"><span class=\"nit-code-name\">docker<\/span> pull bkimminich\/juice-shop<\/span>\n<span class=\"nit-code-line\"><span class=\"nit-code-name\">docker<\/span> run &#8211;rm -p <span class=\"nit-code-number\">3000<\/span>:<span class=\"nit-code-number\">3000<\/span> bkimminich\/juice-shop<\/span>\n<span class=\"nit-code-line\"><span class=\"nit-code-comment\"># Then open http:\/\/localhost:3000<\/span><\/span>\n<\/div>\n<\/div>\n  <div class=\"nit-callout nit-callout--warning\"><p class=\"nit-callout__title\">Keep the target controlled<\/p><p>Do not use an ordinary public website as your training target. The point of Juice Shop is that the vulnerable environment was created specifically for learning. <a href=\"#source-11\" aria-label=\"Reference 11\">[11]<\/a><\/p><\/div>\n  <div class=\"nit-action-strip\"><p><strong>Completion test:<\/strong> Your finding contains scope \u2192 evidence \u2192 explanation \u2192 impact \u2192 recommendation \u2192 retest plan.<\/p><\/div>\n<\/section>\n\n<section id=\"project-8\">\n  <h2>Project 8: Conduct a beginner security assessment<\/h2>\n  <p><strong>Difficulty:<\/strong> Intermediate beginner \u00b7 <strong>Coding:<\/strong> Optional \u00b7 <strong>Time:<\/strong> Several sessions \u00b7 <strong>Output:<\/strong> complete assessment report<\/p>\n  <p>This capstone combines the earlier projects. The purpose is not to add another tool; it is to show that you can plan, collect evidence, prioritise findings, make a safe improvement and verify the result.<\/p>\n  <div class=\"nit-callout nit-callout--info\"><p class=\"nit-callout__title\">Scenario<\/p><p>Create a fictional <strong>Lakeview Learning Centre<\/strong> containing one Windows test computer, one Linux VM, a local network, a local Juice Shop instance and test accounts. Everything remains inside your controlled lab.<\/p><\/div>\n  <div class=\"nit-pg-reasons\" aria-label=\"Project 8 capstone assessment workflow\">\n<div><span>01<\/span><h3>Define scope<\/h3><p>List the Windows test system, Linux VM, local Juice Shop and laboratory network as in scope. Explicitly exclude real school systems, public sites and unrelated networks.<\/p><\/div>\n<div><span>02<\/span><h3>Establish the baseline<\/h3><p>Document assets, accounts, important services, firewall state and network relationships.<\/p><\/div>\n<div><span>03<\/span><h3>Review the network<\/h3><p>Identify expected communication and unnecessary exposure.<\/p><\/div>\n<div><span>04<\/span><h3>Review configuration<\/h3><p>Check accounts, administrator privileges, updates, sharing, firewall and remote access.<\/p><\/div>\n<div><span>05<\/span><h3>Generate one controlled event<\/h3><p>Create and investigate a failed login using the Project 6 method.<\/p><\/div>\n<div><span>06<\/span><h3>Include one web finding<\/h3><p>Use only the intentionally vulnerable local application.<\/p><\/div>\n<div><span>07<\/span><h3>Prioritise<\/h3><p>Use High \/ Medium \/ Low only when you can explain why the finding deserves that priority.<\/p><\/div>\n<div><span>08<\/span><h3>Correct one problem<\/h3><p>Choose something you can safely modify and record before \u2192 change \u2192 after.<\/p><\/div>\n<div><span>09<\/span><h3>Retest<\/h3><p>Repeat the relevant check. If the problem remains, record that the remediation did not succeed.<\/p><\/div>\n<div><span>10<\/span><h3>Write the report<\/h3><p>Include objective, scope, environment, assets, methods, findings, evidence, priority, recommendations, remediation, retest, limitations and lessons learnt.<\/p><\/div>\n<\/div>\n  <div class=\"nit-table-wrap\"><table class=\"nit-table\"><thead><tr><th scope=\"col\">Finding<\/th><th scope=\"col\">Priority<\/th><th scope=\"col\">Reason<\/th><\/tr><\/thead><tbody><tr><td>Unnecessary administrator account<\/td><td>High<\/td><td>Provides elevated access that is not required<\/td><\/tr><tr><td>Unnecessary shared folder<\/td><td>Medium<\/td><td>Expands access to data<\/td><\/tr><tr><td>Pending security update<\/td><td>Medium<\/td><td>Security fixes may be missing<\/td><\/tr><tr><td>Documentation error<\/td><td>Low<\/td><td>Limited direct security effect<\/td><\/tr><\/tbody><\/table><\/div><p class=\"nit-table-note\">On a small screen, swipe the table sideways to see every column.<\/p>\n  <div class=\"nit-action-strip\"><p><strong>Completion test:<\/strong> Another learner can read the report and explain what you assessed, what you found, why it mattered, what changed and whether the correction worked.<\/p><\/div>\n<\/section>\n\n<section class=\"nit-section-panel\" id=\"extra-projects\">\n  <h2>Three extra beginner projects if you want a different cybersecurity direction<\/h2>\n  <div class=\"nit-module-grid\">\n    <article class=\"nit-module-card\"><div class=\"nit-module-card__head\"><span class=\"nit-module-card__number\">A<\/span><h3>Access-control review<\/h3><\/div><p>Create a fictional school with Administrator, Finance, Instructor and Student roles. Build a permission matrix, introduce one excessive permission, correct it and explain the risk.<\/p><p class=\"nit-module-card__outcome\">Introduces identity and access management.<\/p><\/article>\n    <article class=\"nit-module-card\"><div class=\"nit-module-card__head\"><span class=\"nit-module-card__number\">B<\/span><h3>Five-item risk register<\/h3><\/div><p>List five fictional assets, threats or weaknesses, possible impact, existing controls and a sensible next action.<\/p><p class=\"nit-module-card__outcome\">Introduces GRC and risk reasoning.<\/p><\/article>\n    <article class=\"nit-module-card\"><div class=\"nit-module-card__head\"><span class=\"nit-module-card__number\">C<\/span><h3>Backup and restore test<\/h3><\/div><p>Create harmless files, back them up, delete or alter one, restore it and verify the restored copy.<\/p><p class=\"nit-module-card__outcome\">Proves recovery rather than merely \u201chaving a backup\u201d.<\/p><\/article>\n  <\/div>\n<\/section>\n\n<section id=\"choose-project\">\n  <h2>Which cybersecurity project should you build first?<\/h2>\n  <div class=\"nit-table-wrap\"><table class=\"nit-table\"><thead><tr><th scope=\"col\">Your starting point<\/th><th scope=\"col\">Recommended route<\/th><th scope=\"col\">Why<\/th><\/tr><\/thead><tbody><tr><td>Complete beginner<\/td><td>1 \u2192 3 \u2192 2<\/td><td>Learn the system and network before interpreting more complex evidence.<\/td><\/tr><tr><td>School-age learner<\/td><td>1 \u2192 4 \u2192 3<\/td><td>Safe, supervised projects with low hardware demands.<\/td><\/tr><tr><td>No programming experience<\/td><td>1 \u2192 2 \u2192 3 \u2192 4 \u2192 6<\/td><td>Build practical skills without making code a barrier.<\/td><\/tr><tr><td>Interested in SOC analysis<\/td><td>2 \u2192 6 \u2192 8<\/td><td>Traffic, logs, timelines and triage.<\/td><\/tr><tr><td>Interested in ethical hacking<\/td><td>1 \u2192 2 \u2192 3 \u2192 7<\/td><td>Understand networks and systems before controlled security testing.<\/td><\/tr><tr><td>Interested in GRC<\/td><td>3 \u2192 Access review \u2192 Risk register \u2192 8<\/td><td>Configuration, controls, evidence and risk decisions.<\/td><\/tr><tr><td>Interested in automation<\/td><td>5 \u2192 extend gradually<\/td><td>Start with one security idea and automate it well.<\/td><\/tr><\/tbody><\/table><\/div><p class=\"nit-table-note\">On a small screen, swipe the table sideways to see every column.<\/p>\n<\/section>\n\n<section class=\"nit-section-panel\" id=\"troubleshooting\">\n  <h2>How to troubleshoot a cybersecurity project instead of copying the answer<\/h2>\n  <p>Real systems will not always match a tutorial screenshot. Treat that difference as evidence.<\/p>\n  <div class=\"nit-table-wrap\"><table class=\"nit-table\"><thead><tr><th scope=\"col\">Problem<\/th><th scope=\"col\">First question to ask<\/th><\/tr><\/thead><tbody><tr><td>Command gives no expected result<\/td><td>Am I testing the correct system, address or interface?<\/td><\/tr><tr><td>Wireshark traffic looks different<\/td><td>Is another protocol such as QUIC being used?<\/td><\/tr><tr><td>No Windows event appears<\/td><td>Am I checking the correct Security log and computer?<\/td><\/tr><tr><td>Python script fails<\/td><td>What exact error and line are reported?<\/td><\/tr><tr><td>Scan shows an unexpected service<\/td><td>What software owns the service and why is it running?<\/td><\/tr><tr><td>A fix appears ineffective<\/td><td>Did I actually repeat the same test after the change?<\/td><\/tr><tr><td>VMs cannot communicate<\/td><td>Does the virtual network configuration match the lab design?<\/td><\/tr><\/tbody><\/table><\/div><p class=\"nit-table-note\">On a small screen, swipe the table sideways to see every column.<\/p>\n  <div class=\"nit-callout nit-callout--success\"><p class=\"nit-callout__title\">Keep a \u201cwhat went wrong\u201d section<\/p><p>Record what you expected, what happened, what you checked and what you learnt. Troubleshooting often demonstrates more understanding than a perfectly copied exercise.<\/p><\/div>\n<\/section>\n\n<section id=\"portfolio\">\n  <h2>How to turn a lab into portfolio evidence<\/h2>\n  <div class=\"nit-pg-reasons\" aria-label=\"Cybersecurity portfolio write-up structure\">\n<div><span>01<\/span><h3>Problem<\/h3><p>What were you trying to understand or improve?<\/p><\/div>\n<div><span>02<\/span><h3>Environment<\/h3><p>Where did the work happen, and what was authorised?<\/p><\/div>\n<div><span>03<\/span><h3>Method<\/h3><p>What did you do and why?<\/p><\/div>\n<div><span>04<\/span><h3>Evidence<\/h3><p>Which logs, captures, screenshots, settings or code support the result?<\/p><\/div>\n<div><span>05<\/span><h3>Decision<\/h3><p>What does the evidence mean?<\/p><\/div>\n<div><span>06<\/span><h3>Result<\/h3><p>What changed, and was the result expected?<\/p><\/div>\n<div><span>07<\/span><h3>Retest<\/h3><p>Did the improvement actually work?<\/p><\/div>\n<div><span>08<\/span><h3>Reflection<\/h3><p>What failed, what are the limitations and what would you improve next?<\/p><\/div>\n<\/div>\n  <h3>What should never appear in a public cybersecurity portfolio?<\/h3>\n  <ul class=\"nit-choice-list\">\n    <li>Passwords, API keys, private keys, session tokens or cookies.<\/li>\n    <li>Real student, customer or employee data.<\/li>\n    <li>Private email conversations or confidential organisation information.<\/li>\n    <li>Unnecessary public IP addresses, internal hostnames or raw packet captures containing private data.<\/li>\n    <li>Security weaknesses from systems you do not own or have authority to disclose.<\/li>\n  <\/ul>\n  <div class=\"nit-callout nit-callout--warning\"><p class=\"nit-callout__title\">Sanitise before you publish<\/p><p>Use placeholders such as <code>192.168.x.x<\/code> and <code>student@example.test<\/code> where real values do not need to be disclosed. A cybersecurity portfolio should demonstrate judgement, not create a new security problem.<\/p><\/div>\n  <h3>Use a simple README structure<\/h3>\n  <p>A project README should let another person understand the work without opening every screenshot first.<\/p>\n  <div class=\"nit-code-window\" aria-label=\"Suggested cybersecurity project README structure\"><div class=\"nit-code-window__bar\"><span class=\"nit-code-window__dot\"><\/span><span class=\"nit-code-window__dot\"><\/span><span class=\"nit-code-window__dot\"><\/span><span class=\"nit-code-window__file\">README.md<\/span><\/div><div class=\"nit-code-window__body\"><span class=\"nit-code-line\"># Project title<\/span><span class=\"nit-code-line\">## Objective<\/span><span class=\"nit-code-line\">## Scope and authorisation<\/span><span class=\"nit-code-line\">## Environment and tools<\/span><span class=\"nit-code-line\">## Baseline<\/span><span class=\"nit-code-line\">## Steps performed<\/span><span class=\"nit-code-line\">## Evidence and findings<\/span><span class=\"nit-code-line\">## Remediation and retest<\/span><span class=\"nit-code-line\">## Limitations<\/span><span class=\"nit-code-line\">## What I learnt<\/span><\/div><\/div>\n  <h3>Five questions you should be able to answer<\/h3>\n  <ul class=\"nit-choice-list\"><li>What were you trying to accomplish?<\/li><li>Why did you choose that method or tool?<\/li><li>What went wrong or differed from your expectation?<\/li><li>What evidence supported your conclusion?<\/li><li>What would you improve if you repeated the project?<\/li><\/ul>\n<\/section>\n\n<section class=\"nit-section-panel\" id=\"project-score\">\n  <h2>The 20-point beginner cybersecurity project score<\/h2>\n  <p>Give yourself <strong>0 = missing<\/strong>, <strong>1 = partly demonstrated<\/strong>, or <strong>2 = clearly demonstrated<\/strong>. This is a self-check, not a certification.<\/p>\n  <div class=\"nit-table-wrap\"><table class=\"nit-table\"><thead><tr><th scope=\"col\">Area<\/th><th scope=\"col\">Question<\/th><th scope=\"col\">Score<\/th><\/tr><\/thead><tbody><tr><td>Scope<\/td><td>Did I clearly state what I was authorised to test?<\/td><td>0\u20132<\/td><\/tr><tr><td>Objective<\/td><td>Did I define the security question before using a tool?<\/td><td>0\u20132<\/td><\/tr><tr><td>Baseline<\/td><td>Did I record the starting condition?<\/td><td>0\u20132<\/td><\/tr><tr><td>Evidence<\/td><td>Did I collect evidence that actually supports the result?<\/td><td>0\u20132<\/td><\/tr><tr><td>Interpretation<\/td><td>Can I explain what the evidence means?<\/td><td>0\u20132<\/td><\/tr><tr><td>Action<\/td><td>Did I make or recommend a sensible improvement?<\/td><td>0\u20132<\/td><\/tr><tr><td>Verification<\/td><td>Did I retest instead of assuming the change worked?<\/td><td>0\u20132<\/td><\/tr><tr><td>Troubleshooting<\/td><td>Did I document an unexpected result or problem honestly?<\/td><td>0\u20132<\/td><\/tr><tr><td>Limitations<\/td><td>Did I state what my evidence cannot prove?<\/td><td>0\u20132<\/td><\/tr><tr><td>Communication<\/td><td>Could another person understand my report?<\/td><td>0\u20132<\/td><\/tr><\/tbody><\/table><\/div><p class=\"nit-table-note\">On a small screen, swipe the table sideways to see every column.<\/p>\n  <div class=\"nit-curriculum-grid\">\n    <article class=\"nit-curriculum-card\"><span class=\"nit-curriculum-card__period\">0\u20137 points<\/span><h3>Exercise stage<\/h3><p>You completed activity, but the evidence and reasoning still need work.<\/p><\/article>\n    <article class=\"nit-curriculum-card\"><span class=\"nit-curriculum-card__period\">8\u201314 points<\/span><h3>Useful beginner project<\/h3><p>You can demonstrate practical work, but some areas need stronger explanation or verification.<\/p><\/article>\n    <article class=\"nit-curriculum-card\"><span class=\"nit-curriculum-card__period\">15\u201320 points<\/span><h3>Well-structured project<\/h3><p>You demonstrate both technical activity and the reasoning behind it.<\/p><\/article>\n  <\/div>\n<\/section>\n\n<section id=\"cv-evidence\">\n  <h2>How to describe a cybersecurity project on your CV<\/h2>\n  <div class=\"nit-reason-grid\">\n    <article class=\"nit-reason-card\"><span class=\"nit-reason-card__number\">01<\/span><div><h3>Instead of \u201cUsed Wireshark\u201d<\/h3><p>Captured and analysed authorised network traffic, identified DNS and encrypted application traffic, documented communicating endpoints and explained the observed protocol flow.<\/p><\/div><\/article>\n    <article class=\"nit-reason-card\"><span class=\"nit-reason-card__number\">02<\/span><div><h3>Instead of \u201cUsed Event Viewer\u201d<\/h3><p>Generated controlled Windows authentication failures, analysed Security Events 4625 and 4624, built an event timeline and documented why the simulated activity did not require escalation.<\/p><\/div><\/article>\n    <article class=\"nit-reason-card\"><span class=\"nit-reason-card__number\">03<\/span><div><h3>Instead of \u201cLearnt Juice Shop\u201d<\/h3><p>Assessed an intentionally vulnerable local web application, documented an authorised security finding, explained its impact and produced a remediation and retest plan.<\/p><\/div><\/article>\n  <\/div>\n  <p>Only use a CV statement that accurately describes work you genuinely completed. NIT&#8217;s separate review of Kenyan cybersecurity roles also shows that security work extends beyond offensive testing into areas including security operations, incident response, risk, compliance, monitoring and log analysis. <a href=\"#source-14\" aria-label=\"Reference 14\">[14]<\/a><\/p>\n<\/section>\n\n<section class=\"nit-section-panel\" id=\"faq\">\n  <h2>Frequently asked questions<\/h2>\n  <div class=\"nit-faq\">\n    <details class=\"nit-faq__item\"><summary>What is the best cybersecurity project for a complete beginner?<\/summary><div class=\"nit-faq__answer\"><p>Start by mapping your own computer and small practice environment. It introduces devices, interfaces, IP addresses, services and documentation without requiring advanced coding or offensive-security tools.<\/p><\/div><\/details>\n    <details class=\"nit-faq__item\"><summary>Can I practise cybersecurity without coding?<\/summary><div class=\"nit-faq__answer\"><p>Yes. Network mapping, Wireshark analysis, system hardening, phishing investigation and Windows log analysis can all begin without programming. Coding becomes increasingly useful for automation and tool building.<\/p><\/div><\/details>\n    <details class=\"nit-faq__item\"><summary>Can I complete cybersecurity projects on one laptop?<\/summary><div class=\"nit-faq__answer\"><p>Yes. Most projects in this guide can start on one computer. Virtual machines and containers can add isolated systems later when your hardware can support them.<\/p><\/div><\/details>\n    <details class=\"nit-faq__item\"><summary>Do I need Kali Linux?<\/summary><div class=\"nit-faq__answer\"><p>No. Kali Linux is useful for some security-testing tasks, but cybersecurity also involves ordinary Windows and Linux systems, networking, access controls, logs, hardening, investigation and reporting.<\/p><\/div><\/details>\n    <details class=\"nit-faq__item\"><summary>What project can a school-age learner build?<\/summary><div class=\"nit-faq__answer\"><p>Good starting projects include mapping an owned practice environment, analysing safe network traffic, hardening a test computer and investigating a synthetic phishing message. Use owned or supervised systems.<\/p><\/div><\/details>\n    <details class=\"nit-faq__item\"><summary>Which project is best for a future SOC analyst?<\/summary><div class=\"nit-faq__answer\"><p>The Windows login investigation develops log analysis, timelines, context and triage. Wireshark traffic analysis provides another useful foundation.<\/p><\/div><\/details>\n    <details class=\"nit-faq__item\"><summary>Which project is best for ethical hacking?<\/summary><div class=\"nit-faq__answer\"><p>Use an intentionally vulnerable application such as OWASP Juice Shop inside a controlled environment. It is specifically designed for security training. <a href=\"#source-11\" aria-label=\"Reference 11\">[11]<\/a><\/p><\/div><\/details>\n    <details class=\"nit-faq__item\"><summary>How many projects does a beginner need?<\/summary><div class=\"nit-faq__answer\"><p>Start with a few projects completed properly. Three strong projects you understand deeply are more useful than a large collection of copied exercises.<\/p><\/div><\/details>\n  <\/div>\n<\/section>\n\n<section id=\"main-lesson\">\n  <h2>The main lesson: measure progress by what you can explain<\/h2>\n  <p>A beginner might say, <strong>\u201cI found three open ports.\u201d<\/strong> A stronger learner says, <strong>\u201cI identified the services using those ports, confirmed which ones were expected, investigated one unnecessary exposure, changed the configuration and repeated the test to verify the result.\u201d<\/strong><\/p>\n  <p>A beginner might say, <strong>\u201cI found Event 4625.\u201d<\/strong> A stronger learner says, <strong>\u201cI compared failed and successful logons, matched the timestamps with my controlled test and concluded that the activity did not require escalation.\u201d<\/strong><\/p>\n  <p>A beginner might say, <strong>\u201cI solved a Juice Shop challenge.\u201d<\/strong> A stronger learner says, <strong>\u201cI documented expected behaviour, demonstrated the weakness in an authorised lab, explained the impact, recommended a correction and wrote a retest plan.\u201d<\/strong><\/p>\n  <div class=\"nit-callout nit-callout--success\"><p class=\"nit-callout__title\">Use the same cycle repeatedly<\/p><p><strong>Understand \u2192 observe \u2192 investigate \u2192 improve \u2192 retest \u2192 document.<\/strong> That is how small exercises become practical cybersecurity skills.<\/p><\/div>\n<\/section>\n\n<section aria-labelledby=\"register-title\" class=\"nit-pg-enrol\" id=\"register\">\n  <div class=\"nit-pg-enrol__copy\">\n    <p class=\"nit-pg-eyebrow\">Build practical skills with guided training<\/p>\n    <h2 id=\"register-title\">Register for Cybersecurity Training at Newton Institute of Technology<\/h2>\n    <p>NIT&#8217;s Cybersecurity programme develops practical skills in computer systems, networking, Linux, system hardening, authorised security testing, monitoring, incident response, scripting and technical reporting. Institutional training is followed by compulsory industrial attachment. <strong>[13]<\/strong><\/p>\n  <\/div>\n  <div aria-label=\"Cybersecurity course details\" class=\"nit-pg-enrol__details\">\n    <p><span>Institutional training<\/span><strong>6 months \u00b7 <a href=\"#source-13\">[13]<\/a><\/strong><\/p>\n    <p><span>Industrial attachment<\/span><strong>Compulsory 3 months \u00b7 <a href=\"#source-13\">[13]<\/a><\/strong><\/p>\n    <p><span>Study options<\/span><strong>Migori \u00b7 evening \u00b7 online<\/strong><\/p>\n  <\/div>\n  <div class=\"nit-pg-enrol__actions\">\n    <a class=\"nit-pg-button nit-pg-button--gold\" href=\"https:\/\/niteducation.com\/admissions\/\">Register \/ admissions<\/a>\n    <a class=\"nit-pg-button nit-pg-button--outline\" href=\"https:\/\/wa.me\/254713584858?text=Hello%20Newton%20Institute%20of%20Technology.%20I%20would%20like%20to%20register%20for%20the%20Cybersecurity%20Course.\" target=\"_blank\" rel=\"noopener\">WhatsApp +254 713 584 858<\/a>\n  <\/div>\n<\/section>\n\n<section aria-labelledby=\"references-title\" class=\"nit-sources\" id=\"references\">\n  <h2 id=\"references-title\">Sources and references<\/h2>\n  <ol>\n    <li id=\"source-1\"><strong>National Institute of Standards and Technology (NIST).<\/strong> <cite>NICE Framework Components v2.2.0.<\/cite> Used for the Task, Knowledge, Skill, competency-area and work-role approach to cybersecurity capability. Released 28 April 2026; accessed 28 October 2026. <a href=\"https:\/\/www.nist.gov\/news-events\/news\/2026\/04\/nice-releases-nice-framework-components-v220\" rel=\"noopener\" target=\"_blank\">nist.gov<\/a>.<\/li>\n    <li id=\"source-2\"><strong>National Institute of Standards and Technology (NIST).<\/strong> <cite>SP 800-115: Technical Guide to Information Security Testing and Assessment.<\/cite> Used for the assessment lifecycle: planning, testing, analysing findings and mitigation. Accessed 28 October 2026. <a href=\"https:\/\/csrc.nist.gov\/pubs\/sp\/800\/115\/final\" rel=\"noopener\" target=\"_blank\">csrc.nist.gov<\/a>.<\/li>\n    <li id=\"source-3\"><strong>Kenya Law.<\/strong> <cite>Computer Misuse and Cybercrimes Act (Cap. 79C).<\/cite> Used for the Kenyan legal context on unauthorised access and interference. Accessed 28 October 2026. <a href=\"https:\/\/new.kenyalaw.org\/akn\/ke\/act\/2018\/5\/eng@2025-11-04\/source\" rel=\"noopener\" target=\"_blank\">new.kenyalaw.org<\/a>.<\/li>\n    <li id=\"source-4\"><strong>Nmap Project.<\/strong> <cite>Legal Issues.<\/cite> Used for responsible scanning and authorisation guidance. Accessed 28 October 2026. <a href=\"https:\/\/nmap.org\/book\/legal-issues.html\" rel=\"noopener\" target=\"_blank\">nmap.org<\/a>.<\/li>\n    <li id=\"source-5\"><strong>Center for Internet Security.<\/strong> <cite>CIS Critical Security Controls v8.1.<\/cite> Used for asset inventory, secure configuration, account management and audit-log concepts. Accessed 28 October 2026. <a href=\"https:\/\/www.cisecurity.org\/controls\/cis-controls-list\" rel=\"noopener\" target=\"_blank\">cisecurity.org<\/a>.<\/li>\n    <li id=\"source-6\"><strong>Wireshark Foundation.<\/strong> <cite>Wireshark User&#8217;s Guide and QUIC display-filter reference.<\/cite> Used for packet filtering, conversations, endpoints and modern QUIC traffic analysis. Accessed 28 October 2026. <a href=\"https:\/\/www.wireshark.org\/docs\/wsug_html_chunked\/\" rel=\"noopener\" target=\"_blank\">wireshark.org<\/a>; <a href=\"https:\/\/www.wireshark.org\/docs\/dfref\/q\/quic.html\" rel=\"noopener\" target=\"_blank\">QUIC filter reference<\/a>.<\/li>\n    <li id=\"source-7\"><strong>Cybersecurity and Infrastructure Security Agency (CISA).<\/strong> <cite>Secure Our World: Recognize and Report Phishing.<\/cite> Used for phishing indicators and safe-response guidance. Accessed 28 October 2026. <a href=\"https:\/\/www.cisa.gov\/sites\/default\/files\/2024-09\/Secure-Our-World-Phishing-Tip-Sheet.pdf\" rel=\"noopener\" target=\"_blank\">cisa.gov<\/a>.<\/li>\n    <li id=\"source-8\"><strong>Python Software Foundation.<\/strong> <cite>hashlib \u2014 Secure hashes and message digests.<\/cite> Used for the SHA-256 file-integrity example. Accessed 28 October 2026. <a href=\"https:\/\/docs.python.org\/3\/library\/hashlib.html\" rel=\"noopener\" target=\"_blank\">docs.python.org<\/a>.<\/li>\n    <li id=\"source-9\"><strong>Microsoft Learn.<\/strong> <cite>4625(F): An account failed to log on.<\/cite> Used for failed-logon event fields and interpretation. Accessed 28 October 2026. <a href=\"https:\/\/learn.microsoft.com\/windows\/security\/threat-protection\/auditing\/event-4625\" rel=\"noopener\" target=\"_blank\">learn.microsoft.com<\/a>.<\/li>\n    <li id=\"source-10\"><strong>Microsoft Learn.<\/strong> <cite>Audit Logon \/ Windows security event guidance.<\/cite> Used for the 4624 successful-logon and 4625 failed-logon comparison. Accessed 28 October 2026. <a href=\"https:\/\/learn.microsoft.com\/windows\/security\/threat-protection\/auditing\/audit-logon\" rel=\"noopener\" target=\"_blank\">learn.microsoft.com<\/a>.<\/li>\n    <li id=\"source-11\"><strong>OWASP Foundation.<\/strong> <cite>OWASP Juice Shop.<\/cite> Used for the intentionally vulnerable training application and local Docker setup. Accessed 28 October 2026. <a href=\"https:\/\/devguide.owasp.org\/en\/07-training-education\/01-vulnerable-apps\/01-juice-shop\/\" rel=\"noopener\" target=\"_blank\">owasp.org<\/a>.<\/li>\n    <li id=\"source-12\"><strong>OWASP Foundation.<\/strong> <cite>Web Security Testing Guide.<\/cite> Supporting reference for scope-aware web-security testing. Accessed 28 October 2026. <a href=\"https:\/\/owasp.org\/www-project-web-security-testing-guide\/\" rel=\"noopener\" target=\"_blank\">owasp.org<\/a>.<\/li>\n    <li id=\"source-13\"><strong>Newton Institute of Technology.<\/strong> <cite>Cybersecurity Course in Kenya: 6 Months + 3-Month Attachment.<\/cite> Used for current programme duration, attachment and practical training areas. Accessed 28 October 2026. <a href=\"https:\/\/niteducation.com\/resources\/cybersecurity-course-in-kenya\/\">niteducation.com<\/a>.<\/li>\n    <li id=\"source-14\"><strong>Newton Institute of Technology.<\/strong> <cite>Cybersecurity Career in Kenya: Jobs &amp; Skills Employers Need.<\/cite> Supporting internal resource for broader career-family and employer-skills intent. Accessed 28 October 2026. <a href=\"https:\/\/niteducation.com\/resources\/cybersecurity-career-in-kenya\/\">niteducation.com<\/a>.<\/li>\n  <\/ol>\n<\/section>\n<\/div>\n\n<div class=\"nit-article__footer\">\n  <p><strong>Prepared by:<\/strong> Newton Institute of Technology Editorial Team<\/p>\n  <p><strong>Newton Institute of Technology<\/strong> \u00b7 Migori Town, Migori County \u00b7 <a href=\"tel:+254713584858\">+254 713 584 858<\/a> \u00b7 <a href=\"mailto:info@niteducation.com\">info@niteducation.com<\/a><\/p>\n<\/div>\n<\/article>\n","protected":false},"excerpt":{"rendered":"<p>Cybersecurity Beginner Projects Cybersecurity Projects for Beginners:8 Step-by-Step Labs to Build Real Skills understand \u2192 observe \u2192 investigate \u2192 improve \u2192 retest Build practical cybersecurity skills with eight controlled projects you can complete, explain and turn into portfolio evidence\u2014even if you are starting with one laptop and little or no coding experience. Choose a project [&hellip;]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"set","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[30],"tags":[754,755,753],"class_list":["post-3702","post","type-post","status-publish","format-standard","hentry","category-ict","tag-beginner-cybersecurity-projects","tag-cyber-security-projects-for-beginners","tag-cybersecurity-projects-for-beginners"],"_links":{"self":[{"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/posts\/3702","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/comments?post=3702"}],"version-history":[{"count":1,"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/posts\/3702\/revisions"}],"predecessor-version":[{"id":3703,"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/posts\/3702\/revisions\/3703"}],"wp:attachment":[{"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/media?parent=3702"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/categories?post=3702"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/tags?post=3702"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}