{"id":3827,"date":"2026-11-13T10:51:15","date_gmt":"2026-11-13T07:51:15","guid":{"rendered":"https:\/\/niteducation.com\/resources\/?p=3827"},"modified":"2026-11-16T11:54:28","modified_gmt":"2026-11-16T08:54:28","slug":"how-do-ethical-hackers-find-website-vulnerabilities","status":"publish","type":"post","link":"https:\/\/niteducation.com\/resources\/how-do-ethical-hackers-find-website-vulnerabilities\/","title":{"rendered":"How Do Ethical Hackers Find Website Vulnerabilities? Beginner Guide"},"content":{"rendered":"\n<article class=\"nit-article nit-article--pathway-guide nit-article--software\" itemscope=\"\" itemtype=\"https:\/\/schema.org\/BlogPosting\">\n <div aria-labelledby=\"nit-article-title\" class=\"nit-pg-hero\">\n  <div>\n   <p class=\"nit-pg-kicker\">\n    CYBERSECURITY EXPLAINED\n    <span>\n     Beginner website security guide\n    <\/span>\n   <\/p>\n   <p class=\"nit-hero__title\" id=\"nit-article-title\" itemprop=\"headline\">\n    How Do Ethical Hackers Find Website Vulnerabilities? A Beginner&#8217;s Guide\n   <\/p>\n   <p class=\"nit-pg-hero__line\">\n    AUTHORISE\n    \u2192\n    MAP\n    \u2192\n    VERIFY\n    \u2192\n    REPORT\n    \u2192\n    RETEST\n   <\/p>\n   <p class=\"nit-pg-hero__summary\" itemprop=\"description\">\n    How ethical hackers trace a possible website weakness from the first clue to reliable evidence, a clear report and a retested fix\u2014with a fictional student portal and safe examples.\n   <\/p>\n   <div class=\"nit-pg-hero__actions\">\n    <a class=\"nit-pg-button nit-pg-button--gold\" href=\"#quick-answer\">\n     Understand the process\n    <\/a>\n    <a class=\"nit-pg-button nit-pg-button--outline\" href=\"#student-portal\">\n     Explore the classroom walkthrough\n    <\/a>\n   <\/div>\n  <\/div>\n  <div aria-label=\"Visual progression from a possible security finding to a verified result\" class=\"nit-pg-hero__art\">\n   <p>\n    GOOD TESTING USES EVIDENCE\n   <\/p>\n   <div aria-hidden=\"true\" class=\"nit-pg-signpost\">\n    <span class=\"nit-pg-signpost__top\">\n     POSSIBLE CLUE\n    <\/span>\n    <span class=\"nit-pg-signpost__centre\">\n     \u2192\n    <\/span>\n    <span class=\"nit-pg-signpost__bottom\">\n     CHECKED EVIDENCE\n    <\/span>\n   <\/div>\n   <strong>\n    A clue is a question. Reproducible evidence supports the answer.\n   <\/strong>\n  <\/div>\n  <div aria-label=\"Article details\" class=\"nit-pg-hero__meta\">\n   <p>\n    <span>\n     Article\n    <\/span>\n    252 \u00b7 Website security\n   <\/p>\n   <p>\n    <span>\n     Level\n    <\/span>\n    Complete beginners\n   <\/p>\n   <p>\n    <span>\n     Practical scenario\n    <\/span>\n    Fictional student portal\n   <\/p>\n   <p>\n    <span>\n     Updated\n    <\/span>\n    12 November 2026\n   <\/p>\n  <\/div>\n <\/div>\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\">\n     &check;\n    <\/span>\n    <div>\n     <p class=\"nit-quick-answer__label\">\n      Quick answer\n     <\/p>\n     <p class=\"nit-quick-answer__kicker\" id=\"quick-answer-title\">\n      How do ethical hackers discover website vulnerabilities?\n     <\/p>\n    <\/div>\n   <\/div>\n   <div class=\"nit-quick-answer__body\">\n    <p class=\"nit-quick-answer__text\">\n     Hackers find website vulnerabilities by learning how a website works, identifying where security rules might fail and checking observations against those rules. Ethical hackers do this with permission and a defined scope. A scanner alert is a lead\u2014not proof that a website is compromised.\n    <\/p>\n    <ul class=\"nit-quick-answer__signals\">\n     <li>\n      Permission and scope first\n     <\/li>\n     <li>\n      Test the expected security rule\n     <\/li>\n     <li>\n      Evidence, responsible fixes and retesting\n     <\/li>\n    <\/ul>\n   <\/div>\n  <\/section>\n  <p>\n   The methods that reveal weak security controls are not automatically ethical or unethical:\n   <strong>\n    permission, scope, purpose and conduct\n   <\/strong>\n   make the difference. This guide explains the authorised testing process; it does not require you to test somebody else&#8217;s live website.\n  <\/p>\n  <p>\n   Imagine a student portal where Amina and Brian each have private examination results. Both can sign in successfully. But does the server actually check\n   <em>\n    whose\n   <\/em>\n   results each student is allowed to see? That simple question reveals how security testing works: establish the rule, observe what happens, test the boundary safely and explain the result.\n  <\/p>\n  <p>\n   This guide follows that reasoning from start to finish. It uses a\n   <strong>\n    fictional classroom portal and synthetic accounts\n   <\/strong>\n   , not a real school or publicly accessible website.\n  <\/p>\n  <nav aria-labelledby=\"contents-title\" class=\"nit-toc\">\n   <h2 id=\"contents-title\">\n    What you will learn\n   <\/h2>\n   <ol>\n    <li>\n     <a href=\"#vulnerability\">\n      What counts as a website vulnerability?\n     <\/a>\n    <\/li>\n    <li>\n     <a href=\"#web-basics\">\n      Understanding website functions and permissions\n     <\/a>\n    <\/li>\n    <li>\n     <a href=\"#workflow\">\n      The authorised testing workflow\n     <\/a>\n    <\/li>\n    <li>\n     <a href=\"#discovery-methods\">\n      How security clues are found\n     <\/a>\n    <\/li>\n    <li>\n     <a href=\"#proof\">\n      Evidence versus false alarms\n     <\/a>\n    <\/li>\n    <li>\n     <a href=\"#student-portal\">\n      The full student portal walkthrough\n     <\/a>\n    <\/li>\n    <li>\n     <a href=\"#scanners\">\n      What scanning can and cannot prove\n     <\/a>\n    <\/li>\n    <li>\n     <a href=\"#common-weaknesses\">\n      Common types of website weakness\n     <\/a>\n    <\/li>\n    <li>\n     <a href=\"#reports\">\n      Reporting and prioritising findings\n     <\/a>\n    <\/li>\n    <li>\n     <a href=\"#practice\">\n      Safe practice for beginners\n     <\/a>\n    <\/li>\n    <li>\n     <a href=\"#kenya-law\">\n      Kenyan legal and authorisation context\n     <\/a>\n    <\/li>\n    <li>\n     <a href=\"#mistakes\">\n      Avoiding common testing mistakes\n     <\/a>\n    <\/li>\n    <li>\n     <a href=\"#faq\">\n      Frequently asked questions\n     <\/a>\n    <\/li>\n   <\/ol>\n  <\/nav>\n  <section aria-labelledby=\"vulnerability-title\" id=\"vulnerability\">\n   <h2 id=\"vulnerability-title\">\n    What makes a website vulnerable?\n   <\/h2>\n   <p>\n    A\n    <strong>\n     website vulnerability\n    <\/strong>\n    is a weakness in design, code, configuration or operation that may allow a security requirement to fail. Examples include an application disclosing private records to the wrong account, accepting an action a user is not authorised to perform, or exposing sensitive diagnostic information. The\n    <a href=\"https:\/\/wstg.owasp.org\/v4.2\/4-Web_Application_Security_Testing\/\" rel=\"noopener noreferrer\" target=\"_blank\">\n     OWASP Web Security Testing Guide\n    <\/a>\n    <a aria-label=\"Reference 1\" href=\"#ref-1\">\n     [1]\n    <\/a>\n    describes how professionals assess different kinds of web-application controls.\n   <\/p>\n   <p>\n    A bug and a vulnerability are not quite the same. A results page showing the wrong examination date is a bug. A results page letting one student retrieve another student\u2019s private report is a security vulnerability. An unexpected error message could be either, or neither; its meaning depends on what it exposes and what the application is supposed to do.\n   <\/p>\n   <div aria-label=\"Scrollable comparison table\" class=\"nit-pg-table-wrap\" role=\"region\" tabindex=\"0\">\n    <table class=\"nit-pg-table\">\n     <thead>\n      <tr>\n       <th scope=\"col\">\n        Term\n       <\/th>\n       <th scope=\"col\">\n        Plain-English meaning\n       <\/th>\n       <th scope=\"col\">\n        Fictional portal example\n       <\/th>\n      <\/tr>\n     <\/thead>\n     <tbody>\n      <tr>\n       <th scope=\"row\">\n        <strong>\n         Security rule\n        <\/strong>\n       <\/th>\n       <td>\n        What the website must prevent or allow\n       <\/td>\n       <td>\n        A student may read only their own report\n       <\/td>\n      <\/tr>\n      <tr>\n       <th scope=\"row\">\n        <strong>\n         Clue\n        <\/strong>\n       <\/th>\n       <td>\n        Something worth examining\n       <\/td>\n       <td>\n        Two accounts receive unexpectedly similar responses\n       <\/td>\n      <\/tr>\n      <tr>\n       <th scope=\"row\">\n        <strong>\n         Finding\n        <\/strong>\n       <\/th>\n       <td>\n        A documented security observation supported by evidence\n       <\/td>\n       <td>\n        Account B receives Account A\u2019s private report in a controlled test\n       <\/td>\n      <\/tr>\n      <tr>\n       <th scope=\"row\">\n        <strong>\n         Impact\n        <\/strong>\n       <\/th>\n       <td>\n        The harm the weakness could cause\n       <\/td>\n       <td>\n        Exposure of confidential academic records\n       <\/td>\n      <\/tr>\n      <tr>\n       <th scope=\"row\">\n        <strong>\n         Remediation\n        <\/strong>\n       <\/th>\n       <td>\n        The change intended to correct the root cause\n       <\/td>\n       <td>\n        Enforce report ownership on the server\n       <\/td>\n      <\/tr>\n     <\/tbody>\n    <\/table>\n   <\/div>\n   <p class=\"nit-pg-table-note\">\n    On a narrow screen, swipe horizontally to read all columns.\n   <\/p>\n   <p>\n    <strong>\n     The key distinction:\n    <\/strong>\n    a clue tells a tester\n    <em>\n     where to look\n    <\/em>\n    . A confirmed finding explains\n    <em>\n     what failed, under which conditions, and with what evidence\n    <\/em>\n    . A test can also end with\n    <strong>\n     no issue observed\n    <\/strong>\n    or\n    <strong>\n     inconclusive evidence\n    <\/strong>\n    . Not every unusual response is a vulnerability.\n   <\/p>\n  <\/section>\n  <section aria-labelledby=\"web-basics-title\" class=\"nit-section-panel\" id=\"web-basics\">\n   <h2 id=\"web-basics-title\">\n    First understand the website\u2014not just its homepage\n   <\/h2>\n   <p>\n    When you open a page, your browser sends an\n    <strong>\n     HTTP request\n    <\/strong>\n    to a server. The server returns a response and may consult an application, API or database. An API is a way for software components to exchange requests and results. A\n    <strong>\n     session\n    <\/strong>\n    helps the application recognise a signed-in user across requests. These are everyday web fundamentals, explained further in\n    <a href=\"https:\/\/developer.mozilla.org\/en-US\/docs\/Web\/HTTP\/Guides\/Overview\" rel=\"noopener noreferrer\" target=\"_blank\">\n     MDN\u2019s HTTP overview\n    <\/a>\n    <a aria-label=\"Reference 6\" href=\"#ref-6\">\n     [6]\n    <\/a>\n    .\n   <\/p>\n   <p>\n    Picture an imaginary examination portal:\n   <\/p>\n   <ul>\n    <li>\n     The\n     <strong>\n      browser\n     <\/strong>\n     displays the learner\u2019s dashboard.\n    <\/li>\n    <li>\n     The\n     <strong>\n      server\n     <\/strong>\n     receives the request to open a report.\n    <\/li>\n    <li>\n     The\n     <strong>\n      database\n     <\/strong>\n     stores synthetic student records.\n    <\/li>\n    <li>\n     The\n     <strong>\n      permission check\n     <\/strong>\n     decides whether the signed-in account may access the requested record.\n    <\/li>\n   <\/ul>\n   <p>\n    A website can look perfectly normal while one of these server-side checks is missing.\n   <\/p>\n   <h3>\n    Authentication and authorisation are different\n   <\/h3>\n   <p>\n    <strong>\n     Authentication\n    <\/strong>\n    answers, \u201cWhich user signed in?\u201d\n    <strong>\n     Authorisation\n    <\/strong>\n    answers, \u201cWhat may that user do?\u201d Amina\u2019s valid password proves she is Amina; it does not give her permission to see Brian\u2019s marks. Proper authorisation must be enforced by trusted server-side application logic\u2014not merely by hiding a button in the browser.\n    <a href=\"https:\/\/top10.owasp.org\/2025\/A01_2025-Broken_Access_Control\/\" rel=\"noopener noreferrer\" target=\"_blank\">\n     OWASP\u2019s Broken Access Control guidance\n    <\/a>\n    <a aria-label=\"Reference 5\" href=\"#ref-5\">\n     [5]\n    <\/a>\n    describes this distinction in practice.\n   <\/p>\n   <p>\n    For example, the fictional request below simply means a signed-in account has asked for its own report. It is\n    <em>\n     not\n    <\/em>\n    a test against a real domain:\n   <\/p>\n   <div aria-label=\"Illustrative fictional website security training example\" class=\"nit-code-window\">\n    <div class=\"nit-code-window__bar\">\n     <span aria-hidden=\"true\" class=\"nit-code-window__dot\">\n     <\/span>\n     <span aria-hidden=\"true\" class=\"nit-code-window__dot\">\n     <\/span>\n     <span aria-hidden=\"true\" class=\"nit-code-window__dot\">\n     <\/span>\n     <span class=\"nit-code-window__file\">\n      fictional-request.txt\n     <\/span>\n    <\/div>\n    <div aria-label=\"Scrollable illustrative code sample\" class=\"nit-code-window__body\" role=\"region\" tabindex=\"0\">\n     <span class=\"nit-code-line\">\n      GET \/my-results HTTP\/1.1\n     <\/span>\n     <span class=\"nit-code-line\">\n      Host: student-portal.example\n     <\/span>\n     <span class=\"nit-code-line\">\n      Cookie: session=DEMO-ONLY\n     <\/span>\n    <\/div>\n   <\/div>\n   <p>\n    The\n    <code>\n     .example\n    <\/code>\n    domain is\n    <a href=\"https:\/\/datatracker.ietf.org\/doc\/html\/rfc6761#section-6.5\" rel=\"noopener noreferrer\" target=\"_blank\">\n     reserved for illustrations\n    <\/a>\n    <a aria-label=\"Reference 14\" href=\"#ref-14\">\n     [14]\n    <\/a>\n    . A response such as\n    <code>\n     200 OK\n    <\/code>\n    means a request succeeded at the HTTP level; it does\n    <strong>\n     not\n    <\/strong>\n    , on its own, prove that the right person received the right information.\n   <\/p>\n   <h3>\n    Build a simple map of what needs protection\n   <\/h3>\n   <p>\n    Before looking for weaknesses, ask what the application must protect and where those rules are enforced. This is sometimes called mapping the\n    <strong>\n     attack surface\n    <\/strong>\n    : the exposed functions and components that might need security checks. In an authorised assessment, the map is limited to the systems and features the owner has approved.\n   <\/p>\n   <div aria-label=\"Scrollable comparison table\" class=\"nit-pg-table-wrap\" role=\"region\" tabindex=\"0\">\n    <table class=\"nit-pg-table\">\n     <thead>\n      <tr>\n       <th scope=\"col\">\n        Area to understand\n       <\/th>\n       <th scope=\"col\">\n        Fictional portal question\n       <\/th>\n       <th scope=\"col\">\n        Possible security rule\n       <\/th>\n      <\/tr>\n     <\/thead>\n     <tbody>\n      <tr>\n       <th scope=\"row\">\n        <strong>\n         Login and sessions\n        <\/strong>\n       <\/th>\n       <td>\n        How does the site remember that a student signed in?\n       <\/td>\n       <td>\n        A signed-out visitor cannot see protected reports\n       <\/td>\n      <\/tr>\n      <tr>\n       <th scope=\"row\">\n        <strong>\n         Records and downloads\n        <\/strong>\n       <\/th>\n       <td>\n        Where do students retrieve their results and receipts?\n       <\/td>\n       <td>\n        A student may retrieve only their own records\n       <\/td>\n      <\/tr>\n      <tr>\n       <th scope=\"row\">\n        <strong>\n         Forms and data changes\n        <\/strong>\n       <\/th>\n       <td>\n        Can a student update contact information?\n       <\/td>\n       <td>\n        Changing personal details requires the right account\n       <\/td>\n      <\/tr>\n      <tr>\n       <th scope=\"row\">\n        <strong>\n         Administrative functions\n        <\/strong>\n       <\/th>\n       <td>\n        Who may publish marks or change a student record?\n       <\/td>\n       <td>\n        A student cannot perform staff-only actions\n       <\/td>\n      <\/tr>\n      <tr>\n       <th scope=\"row\">\n        <strong>\n         APIs and background requests\n        <\/strong>\n       <\/th>\n       <td>\n        Do app requests use the same permission rules as visible pages?\n       <\/td>\n       <td>\n        Every relevant server endpoint checks the user&#8217;s authority\n       <\/td>\n      <\/tr>\n     <\/tbody>\n    <\/table>\n   <\/div>\n   <p class=\"nit-pg-table-note\">\n    On a narrow screen, swipe horizontally to read all columns.\n   <\/p>\n   <p>\n    For example, a portal may hide a report-download button from Brian but still accept an unauthorised download request. The visible interface is therefore only one part of the assessment. OWASP&#8217;s\n    <a href=\"https:\/\/asvs.owasp.org\/\" rel=\"noopener noreferrer\" target=\"_blank\">\n     Application Security Verification Standard 5.0.0\n    <\/a>\n    <a aria-label=\"Reference 9\" href=\"#ref-9\">\n     [9]\n    <\/a>\n    provides a separate catalogue of security requirements that developers and testers can use to define such expectations.\n   <\/p>\n  <\/section>\n  <section aria-labelledby=\"workflow-title\" id=\"workflow\">\n   <h2 id=\"workflow-title\">\n    How do ethical hackers actually find weaknesses? A practical workflow\n   <\/h2>\n   <p>\n    Security work is not a single magic scan. In a classroom, it can be taught as seven connected activities. Professional engagements may perform them in another order or repeat them as new information appears; the\n    <a href=\"https:\/\/wstg.owasp.org\/latest\/3-The_OWASP_Testing_Framework\/0-The_Web_Security_Testing_Framework\/\" rel=\"noopener noreferrer\" target=\"_blank\">\n     OWASP testing framework\n    <\/a>\n    <a aria-label=\"Reference 3\" href=\"#ref-3\">\n     [3]\n    <\/a>\n    is flexible rather than a compulsory seven-step sequence.\n   <\/p>\n   <div class=\"nit-module-grid\">\n    <article class=\"nit-module-card\">\n     <div class=\"nit-module-card__head\">\n      <span class=\"nit-module-card__number\">\n       01\n      <\/span>\n      <h3>\n       Authorise and define the scope\n      <\/h3>\n     <\/div>\n     <p>\n      <strong>\n       1. Confirm permission.\n      <\/strong>\n      Agree systems, test accounts, permitted methods, timing and stop conditions\n     <\/p>\n     <p class=\"nit-module-card__outcome\">\n      Output: Written scope and rules\n     <\/p>\n    <\/article>\n    <article class=\"nit-module-card\">\n     <div class=\"nit-module-card__head\">\n      <span class=\"nit-module-card__number\">\n       02\n      <\/span>\n      <h3>\n       Understand and map\n      <\/h3>\n     <\/div>\n     <p>\n      <strong>\n       2. Learn expected behaviour.\n      <\/strong>\n      Ask what each account or feature is supposed to do\n     <\/p>\n     <p>\n      <strong>\n       3. Map the application.\n      <\/strong>\n      Review approved pages, forms, API functions and software components\n     <\/p>\n     <p class=\"nit-module-card__outcome\">\n      Output: A list of security rules; A simple application map\n     <\/p>\n    <\/article>\n    <article class=\"nit-module-card\">\n     <div class=\"nit-module-card__head\">\n      <span class=\"nit-module-card__number\">\n       03\n      <\/span>\n      <h3>\n       Investigate and verify\n      <\/h3>\n     <\/div>\n     <p>\n      <strong>\n       4. Look for clues.\n      <\/strong>\n      Inspect traffic, settings, messages, roles and relevant tool alerts\n     <\/p>\n     <p>\n      <strong>\n       5. Check the hypothesis.\n      <\/strong>\n      Compare expected and observed behaviour with controlled test data\n     <\/p>\n     <p class=\"nit-module-card__outcome\">\n      Output: Questions needing verification; Reproducible evidence or a rejected hypothesis\n     <\/p>\n    <\/article>\n    <article class=\"nit-module-card\">\n     <div class=\"nit-module-card__head\">\n      <span class=\"nit-module-card__number\">\n       04\n      <\/span>\n      <h3>\n       Explain, fix and retest\n      <\/h3>\n     <\/div>\n     <p>\n      <strong>\n       6. Explain the finding.\n      <\/strong>\n      Document affected control, impact and corrective action\n     <\/p>\n     <p>\n      <strong>\n       7. Retest.\n      <\/strong>\n      Verify the correction and normal user functions\n     <\/p>\n     <p class=\"nit-module-card__outcome\">\n      Output: A clear, actionable report; Evidence of the fix under tested conditions\n     <\/p>\n    <\/article>\n   <\/div>\n   <p>\n    Here,\n    <strong>\n     reconnaissance\n    <\/strong>\n    simply means learning what is present and in scope. It may involve information already supplied by a system owner, reading documentation and observing the behaviour of permitted accounts. More intrusive discovery or testing requires explicit authorisation. The\n    <a href=\"https:\/\/wstg.owasp.org\/latest\/4-Web_Application_Security_Testing\/01-Information_Gathering\/00-Information_Gathering_Overview\/\" rel=\"noopener noreferrer\" target=\"_blank\">\n     OWASP information-gathering guidance\n    <\/a>\n    <a aria-label=\"Reference 2\" href=\"#ref-2\">\n     [2]\n    <\/a>\n    explains why an incomplete application map can lead to an incomplete assessment.\n   <\/p>\n  <\/section>\n  <section aria-labelledby=\"discovery-methods-title\" class=\"nit-section-panel\" id=\"discovery-methods\">\n   <h2 id=\"discovery-methods-title\">\n    Where do testers get clues that a website might be insecure?\n   <\/h2>\n   <p>\n    The most useful question is not \u201cWhich hacking tool should I open?\u201d but \u201cWhich security rule might fail here, and what observation would support that suspicion?\u201d\n   <\/p>\n   <div aria-label=\"Scrollable comparison table\" class=\"nit-pg-table-wrap\" role=\"region\" tabindex=\"0\">\n    <table class=\"nit-pg-table\">\n     <thead>\n      <tr>\n       <th scope=\"col\">\n        Possible clue\n       <\/th>\n       <th scope=\"col\">\n        Why it deserves attention\n       <\/th>\n       <th scope=\"col\">\n        What it does\n        <strong>\n         not\n        <\/strong>\n        prove\n       <\/th>\n      <\/tr>\n     <\/thead>\n     <tbody>\n      <tr>\n       <th scope=\"row\">\n        One account appears to receive another account\u2019s data\n       <\/th>\n       <td>\n        The application may be missing a resource-ownership check\n       <\/td>\n       <td>\n        That every record is accessible\n       <\/td>\n      <\/tr>\n      <tr>\n       <th scope=\"row\">\n        An error reveals detailed internal paths or configuration\n       <\/th>\n       <td>\n        Sensitive diagnostic information may be exposed\n       <\/td>\n       <td>\n        That a stranger can take control of the server\n       <\/td>\n      <\/tr>\n      <tr>\n       <th scope=\"row\">\n        A scanner flags a missing security header\n       <\/th>\n       <td>\n        A hardening control may be absent\n       <\/td>\n       <td>\n        That a successful attack is possible in the current circumstances\n       <\/td>\n      <\/tr>\n      <tr>\n       <th scope=\"row\">\n        Software inventory shows an older component\n       <\/th>\n       <td>\n        A known security advisory may apply\n       <\/td>\n       <td>\n        That the installed component is definitely exploitable\n       <\/td>\n      <\/tr>\n      <tr>\n       <th scope=\"row\">\n        A login remains recognised after a sign-out in a controlled test\n       <\/th>\n       <td>\n        Session invalidation may need review\n       <\/td>\n       <td>\n        That all sessions or accounts are affected\n       <\/td>\n      <\/tr>\n      <tr>\n       <th scope=\"row\">\n        A form returns unexpected content\n       <\/th>\n       <td>\n        Input handling or output encoding may need investigation\n       <\/td>\n       <td>\n        That the page necessarily has an exploitable injection vulnerability\n       <\/td>\n      <\/tr>\n     <\/tbody>\n    <\/table>\n   <\/div>\n   <p class=\"nit-pg-table-note\">\n    On a narrow screen, swipe horizontally to read all columns.\n   <\/p>\n   <p>\n    A clue becomes useful when the tester can explain\n    <em>\n     the expectation\n    <\/em>\n    ,\n    <em>\n     the observation\n    <\/em>\n    and\n    <em>\n     the limits of the conclusion\n    <\/em>\n    . For a software-version alert, for instance, the next question is whether the exact installed version and configuration match an applicable advisory. For an access-control clue, the next question is whether the response truly contains another account\u2019s protected data or only harmless shared page content.\n   <\/p>\n   <p>\n    Three particularly useful discovery questions are\n    <strong>\n     what can the user see\n    <\/strong>\n    ,\n    <strong>\n     what can the user change\n    <\/strong>\n    , and\n    <strong>\n     what should happen when their permission ends\n    <\/strong>\n    . These reveal different classes of problems: private data exposure, unauthorised actions and expired-session handling. A tester documents the expected rule first, then chooses only the least intrusive approved check that can answer it.\n   <\/p>\n   <p>\n    <strong>\n     One important distinction:\n    <\/strong>\n    seeing an endpoint in a browser or proxy does not mean it is insecure. An endpoint is simply a place where the application accepts a request; its security depends on what it allows and what controls it enforces.\n   <\/p>\n  <\/section>\n  <section aria-labelledby=\"proof-title\" id=\"proof\">\n   <h2 id=\"proof-title\">\n    How do testers separate a genuine vulnerability from a false alarm?\n   <\/h2>\n   <p>\n    Suppose a scanning tool highlights a missing header. That is a finding about an observable response header, but it does not automatically establish an exploitable security flaw or its severity. A tester must interpret it in context.\n   <\/p>\n   <p>\n    Use this four-question evidence check:\n   <\/p>\n   <div class=\"nit-reason-grid\">\n    <article class=\"nit-reason-card\">\n     <span class=\"nit-reason-card__number\">\n      01\n     <\/span>\n     <div>\n      <h3>\n       What rule should hold?\n      <\/h3>\n      <p>\n       For example, only a report owner should receive that report\u2019s content.\n      <\/p>\n     <\/div>\n    <\/article>\n    <article class=\"nit-reason-card\">\n     <span class=\"nit-reason-card__number\">\n      02\n     <\/span>\n     <div>\n      <h3>\n       What did we observe?\n      <\/h3>\n      <p>\n       Record the account role, relevant request, response and outcome using synthetic data.\n      <\/p>\n     <\/div>\n    <\/article>\n    <article class=\"nit-reason-card\">\n     <span class=\"nit-reason-card__number\">\n      03\n     <\/span>\n     <div>\n      <h3>\n       Can the result be reproduced safely?\n      <\/h3>\n      <p>\n       Repeat only the necessary approved check and rule out test-account or configuration mistakes.\n      <\/p>\n     <\/div>\n    <\/article>\n    <article class=\"nit-reason-card\">\n     <span class=\"nit-reason-card__number\">\n      04\n     <\/span>\n     <div>\n      <h3>\n       What conclusion is justified?\n      <\/h3>\n      <p>\n       Describe the specific control failure, not a dramatic claim about the whole website.\n      <\/p>\n     <\/div>\n    <\/article>\n   <\/div>\n   <p>\n    A\n    <strong>\n     false positive\n    <\/strong>\n    is an alert that does not represent the claimed issue in the tested context. A\n    <strong>\n     false negative\n    <\/strong>\n    is an existing weakness that a tool or test misses. Neither can be eliminated merely by running more tools. A high-severity label from software does not override the need to check relevance and impact.\n   <\/p>\n   <h3>\n    An evidence ladder: four ways a security check can end\n   <\/h3>\n   <div aria-label=\"Scrollable comparison table\" class=\"nit-pg-table-wrap\" role=\"region\" tabindex=\"0\">\n    <table class=\"nit-pg-table\">\n     <thead>\n      <tr>\n       <th scope=\"col\">\n        Result\n       <\/th>\n       <th scope=\"col\">\n        What the evidence supports\n       <\/th>\n       <th scope=\"col\">\n        What the tester should write\n       <\/th>\n      <\/tr>\n     <\/thead>\n     <tbody>\n      <tr>\n       <th scope=\"row\">\n        No issue\n       <\/th>\n       <td>\n        The approved case behaved as expected\n       <\/td>\n       <td>\n        &#8220;Access denied in this tested case&#8221;\u2014not &#8220;the whole site is secure&#8221;\n       <\/td>\n      <\/tr>\n      <tr>\n       <th scope=\"row\">\n        Possible\n       <\/th>\n       <td>\n        An unexpected alert or response needs explanation\n       <\/td>\n       <td>\n        &#8220;Possible issue; confirmation pending&#8221;\n       <\/td>\n      <\/tr>\n      <tr>\n       <th scope=\"row\">\n        Verified\n       <\/th>\n       <td>\n        A reproducible, authorised observation violates a defined security rule\n       <\/td>\n       <td>\n        State the affected function, condition and impact supported by evidence\n       <\/td>\n      <\/tr>\n      <tr>\n       <th scope=\"row\">\n        Unclear\n       <\/th>\n       <td>\n        The tester cannot separate an anomaly from session, cache, configuration or test-data errors\n       <\/td>\n       <td>\n        Record what was tried and why no conclusion is justified\n       <\/td>\n      <\/tr>\n     <\/tbody>\n    <\/table>\n   <\/div>\n   <p class=\"nit-pg-table-note\">\n    On a narrow screen, swipe horizontally to read all columns.\n   <\/p>\n   <p>\n    <strong>\n     Quick example:\n    <\/strong>\n    A publicly accessible school calendar returns\n    <code>\n     200 OK\n    <\/code>\n    : that may be entirely correct. A\n    <code>\n     200 OK\n    <\/code>\n    response that contains only a login page, perhaps after a redirect, is not evidence that private data was exposed. But if a fully documented local lab test shows Brian receiving Amina&#8217;s private marks, the ownership rule failed. A version alert about an old software library stays a\n    <strong>\n     lead\n    <\/strong>\n    until the exact component, applicable advisory and deployment context are checked. No single HTTP status, scanner label or screenshot tells the whole story.\n   <\/p>\n   <p>\n    That is why a report should be more precise than \u201cthe website has been hacked.\u201d A strong description might read:\n    <em>\n     \u201cIn this local test environment, Student B received Student A\u2019s private report, although the documented policy requires denial.\u201d\n    <\/em>\n    The statement identifies the environment, rule, observation and scope.\n   <\/p>\n  <\/section>\n  <section aria-labelledby=\"student-portal-title\" class=\"nit-section-panel\" id=\"student-portal\">\n   <h2 id=\"student-portal-title\">\n    Classroom walkthrough: test a fictional student portal\n   <\/h2>\n   <p>\n    Meet\n    <strong>\n     Lakeview Training Portal\n    <\/strong>\n    \u2014an imaginary application prepared for a supervised lesson. It has two made-up students:\n    <strong>\n     Amina (account A)\n    <\/strong>\n    and\n    <strong>\n     Brian (account B)\n    <\/strong>\n    . Each owns one fake examination report. The instructor has authorised the class to check report access using only these synthetic accounts.\n   <\/p>\n   <div class=\"nit-module-grid\">\n    <article class=\"nit-module-card\">\n     <div class=\"nit-module-card__head\">\n      <span class=\"nit-module-card__number\">\n       01\n      <\/span>\n      <h3>\n       Define the rules\n      <\/h3>\n     <\/div>\n     <p>\n      Steps 1\u20132: establish ownership and write the permitted\/denied test matrix.\n     <\/p>\n     <p class=\"nit-module-card__outcome\">\n      Lesson: check expected behaviour against observed evidence.\n     <\/p>\n    <\/article>\n    <article class=\"nit-module-card\">\n     <div class=\"nit-module-card__head\">\n      <span class=\"nit-module-card__number\">\n       02\n      <\/span>\n      <h3>\n       Observe and compare\n      <\/h3>\n     <\/div>\n     <p>\n      Steps 3\u20134: confirm normal access, then check an approved cross-account boundary.\n     <\/p>\n     <p class=\"nit-module-card__outcome\">\n      Lesson: check expected behaviour against observed evidence.\n     <\/p>\n    <\/article>\n    <article class=\"nit-module-card\">\n     <div class=\"nit-module-card__head\">\n      <span class=\"nit-module-card__number\">\n       03\n      <\/span>\n      <h3>\n       Validate and diagnose\n      <\/h3>\n     <\/div>\n     <p>\n      Steps 5\u20136: rule out misleading evidence and identify the missing control.\n     <\/p>\n     <p class=\"nit-module-card__outcome\">\n      Lesson: check expected behaviour against observed evidence.\n     <\/p>\n    <\/article>\n    <article class=\"nit-module-card\">\n     <div class=\"nit-module-card__head\">\n      <span class=\"nit-module-card__number\">\n       04\n      <\/span>\n      <h3>\n       Report and retest\n      <\/h3>\n     <\/div>\n     <p>\n      Step 7: document the result and repeat every expected test after correction.\n     <\/p>\n     <p class=\"nit-module-card__outcome\">\n      Lesson: check expected behaviour against observed evidence.\n     <\/p>\n    <\/article>\n   <\/div>\n   <p>\n    <strong>\n     Scope sheet for this exercise:\n    <\/strong>\n    The included system is the isolated Lakeview Training Portal. The permitted accounts are Amina, Brian and a signed-out visitor. The permitted activity is reading synthetic report data and checking the pre-agreed access outcomes. Real school websites, personal records, password guessing, destructive tests and unrelated systems are excluded. The instructor will stop testing if unexpected data or functionality appears.\n   <\/p>\n   <h3>\n    Step 1: Write the security rule before testing\n   <\/h3>\n   <p>\n    Amina may read Amina\u2019s report. Brian may read Brian\u2019s report. Neither may read the other\u2019s report. A visitor who has not signed in may read neither report.\n   <\/p>\n   <h3>\n    Step 2: Record the expected outcomes\n   <\/h3>\n   <div aria-label=\"Scrollable comparison table\" class=\"nit-pg-table-wrap\" role=\"region\" tabindex=\"0\">\n    <table class=\"nit-pg-table\">\n     <thead>\n      <tr>\n       <th scope=\"col\">\n        Account making request\n       <\/th>\n       <th scope=\"col\">\n        Requested fictional report\n       <\/th>\n       <th scope=\"col\">\n        Expected result\n       <\/th>\n      <\/tr>\n     <\/thead>\n     <tbody>\n      <tr>\n       <th scope=\"row\">\n        Amina\n       <\/th>\n       <td>\n        Amina\u2019s\n       <\/td>\n       <td>\n        <strong>\n         Allow\n        <\/strong>\n       <\/td>\n      <\/tr>\n      <tr>\n       <th scope=\"row\">\n        Brian\n       <\/th>\n       <td>\n        Brian\u2019s\n       <\/td>\n       <td>\n        <strong>\n         Allow\n        <\/strong>\n       <\/td>\n      <\/tr>\n      <tr>\n       <th scope=\"row\">\n        Brian\n       <\/th>\n       <td>\n        Amina\u2019s\n       <\/td>\n       <td>\n        <strong>\n         Deny\n        <\/strong>\n       <\/td>\n      <\/tr>\n      <tr>\n       <th scope=\"row\">\n        Amina\n       <\/th>\n       <td>\n        Brian\u2019s\n       <\/td>\n       <td>\n        <strong>\n         Deny\n        <\/strong>\n       <\/td>\n      <\/tr>\n      <tr>\n       <th scope=\"row\">\n        Signed-out visitor\n       <\/th>\n       <td>\n        Either report\n       <\/td>\n       <td>\n        <strong>\n         Deny\n        <\/strong>\n       <\/td>\n      <\/tr>\n     <\/tbody>\n    <\/table>\n   <\/div>\n   <p class=\"nit-pg-table-note\">\n    On a narrow screen, swipe horizontally to read all columns.\n   <\/p>\n   <p>\n    These\n    <strong>\n     positive tests\n    <\/strong>\n    (legitimate access) and\n    <strong>\n     negative tests\n    <\/strong>\n    (access that must fail) matter equally. A fix that blocks everyone is not a satisfactory solution.\n   <\/p>\n   <h3>\n    Step 3: Observe ordinary behaviour\n   <\/h3>\n   <p>\n    The instructor signs in to each synthetic account in turn and confirms that each can open its own report. The class notes the user role, requested resource and visible outcome. The purpose is to establish a baseline, not to guess passwords or access unrelated systems.\n   <\/p>\n   <h3>\n    Step 4: Compare an authorised boundary case\n   <\/h3>\n   <p>\n    Inside the local lab, the instructor checks the pre-agreed case in which Brian\u2019s account requests Amina\u2019s\n    <em>\n     synthetic\n    <\/em>\n    report. Two fictional outcomes illustrate how the reasoning changes:\n   <\/p>\n   <div aria-label=\"Illustrative fictional website security training example\" class=\"nit-code-window\">\n    <div class=\"nit-code-window__bar\">\n     <span aria-hidden=\"true\" class=\"nit-code-window__dot\">\n     <\/span>\n     <span aria-hidden=\"true\" class=\"nit-code-window__dot\">\n     <\/span>\n     <span aria-hidden=\"true\" class=\"nit-code-window__dot\">\n     <\/span>\n     <span class=\"nit-code-window__file\">\n      synthetic-test-outcomes.txt\n     <\/span>\n    <\/div>\n    <div aria-label=\"Scrollable illustrative code sample\" class=\"nit-code-window__body\" role=\"region\" tabindex=\"0\">\n     <span class=\"nit-code-line\">\n      EXPECTED SECURITY RULE\n     <\/span>\n     <span class=\"nit-code-line\">\n      Brian requests Amina&#8217;s report  \u2192  access denied\n     <\/span>\n     <span class=\"nit-code-line\">\n      &nbsp;\n     <\/span>\n     <span class=\"nit-code-line\">\n      OBSERVED IN FAULTY TRAINING VERSION\n     <\/span>\n     <span class=\"nit-code-line\">\n      Brian requests Amina&#8217;s report  \u2192  Amina&#8217;s synthetic marks shown\n     <\/span>\n     <span class=\"nit-code-line\">\n      &nbsp;\n     <\/span>\n     <span class=\"nit-code-line\">\n      OBSERVED AFTER CORRECTION\n     <\/span>\n     <span class=\"nit-code-line\">\n      Brian requests Amina&#8217;s report  \u2192  access denied\n     <\/span>\n    <\/div>\n   <\/div>\n   <p>\n    The\n    <em>\n     content and account ownership\n    <\/em>\n    matter here\u2014not merely the HTTP status code. A properly implemented application may return\n    <code>\n     403 Forbidden\n    <\/code>\n    or deliberately use\n    <code>\n     404 Not Found\n    <\/code>\n    ; either can be consistent with denying access depending on its design. A\n    <code>\n     200 OK\n    <\/code>\n    response could contain an ordinary login page rather than somebody\u2019s protected report. Look at the actual, approved evidence.\n   <\/p>\n   <h3>\n    Step 5: Rule out misleading explanations\n   <\/h3>\n   <p>\n    Check that the accounts are distinct, the reports are correctly assigned, the displayed content is not a cached page from the wrong session, and the instructor has not accidentally granted both students a special teaching role. The observation should be repeatable under documented conditions before being treated as confirmed.\n   <\/p>\n   <p>\n    For example,\n    <strong>\n     seeing Amina&#8217;s name\n    <\/strong>\n    on a shared class notice does not prove that Brian received her private report.\n    <strong>\n     Seeing Amina&#8217;s synthetic marks inside the protected report response\n    <\/strong>\n    , while signed in as Brian, is a different observation. The instructor verifies which account is active and which record the response actually contains before drawing the conclusion.\n   <\/p>\n   <h3>\n    Step 6: Explain the likely root cause\n   <\/h3>\n   <p>\n    In the fictional faulty version, the server checks whether Brian is signed in but fails to check whether Brian owns the\n    <em>\n     particular report\n    <\/em>\n    . The page may hide other students\u2019 links, but the server still needs to enforce the ownership rule when handling the request. The same rule should apply whether a report is opened in the page, retrieved through an approved API, or downloaded as a file. OWASP&#8217;s\n    <a href=\"https:\/\/cheatsheetseries.owasp.org\/cheatsheets\/Authorization_Cheat_Sheet.html\" rel=\"noopener noreferrer\" target=\"_blank\">\n     Authorisation Cheat Sheet\n    <\/a>\n    <a aria-label=\"Reference 10\" href=\"#ref-10\">\n     [10]\n    <\/a>\n    recommends deny-by-default and server-side enforcement.\n   <\/p>\n   <p>\n    A defensive implementation can be understood with this simplified pseudocode:\n   <\/p>\n   <div aria-label=\"Illustrative fictional website security training example\" class=\"nit-code-window\">\n    <div class=\"nit-code-window__bar\">\n     <span aria-hidden=\"true\" class=\"nit-code-window__dot\">\n     <\/span>\n     <span aria-hidden=\"true\" class=\"nit-code-window__dot\">\n     <\/span>\n     <span aria-hidden=\"true\" class=\"nit-code-window__dot\">\n     <\/span>\n     <span class=\"nit-code-window__file\">\n      server-side-authorization-pseudocode.txt\n     <\/span>\n    <\/div>\n    <div aria-label=\"Scrollable illustrative code sample\" class=\"nit-code-window__body\" role=\"region\" tabindex=\"0\">\n     <span class=\"nit-code-line\">\n      if not signed_in(user):\n     <\/span>\n     <span class=\"nit-code-line\">\n      deny_access()\n     <\/span>\n     <span class=\"nit-code-line\">\n      &nbsp;\n     <\/span>\n     <span class=\"nit-code-line\">\n      report = find_report(requested_report_id)\n     <\/span>\n     <span class=\"nit-code-line\">\n      if report is missing:\n     <\/span>\n     <span class=\"nit-code-line\">\n      deny_access()\n     <\/span>\n     <span class=\"nit-code-line\">\n      &nbsp;\n     <\/span>\n     <span class=\"nit-code-line\">\n      if report.owner_id != user.id:\n     <\/span>\n     <span class=\"nit-code-line\">\n      deny_access()\n     <\/span>\n     <span class=\"nit-code-line\">\n      &nbsp;\n     <\/span>\n     <span class=\"nit-code-line\">\n      return report_to_authorised_user(report)\n     <\/span>\n    <\/div>\n   <\/div>\n   <p>\n    This illustrates a principle, not a complete security implementation. Production systems also need appropriate session handling, logging and consistent permission checks across related endpoints.\n   <\/p>\n   <h3>\n    Step 7: Document and retest the fix\n   <\/h3>\n   <p>\n    The class writes a report describing the confirmed lab failure, possible harm if the same defect existed in production and a recommended server-side ownership check. After the developer corrects the training app, the class repeats\n    <strong>\n     all five cases\n    <\/strong>\n    from the expected-results table. Legitimate access still works; cross-account and signed-out access are denied.\n   <\/p>\n   <p>\n    <strong>\n     What this exercise proves:\n    <\/strong>\n    the particular access rule works or fails under these synthetic test conditions. It does\n    <em>\n     not\n    <\/em>\n    establish that every function in the application has been tested or that all other security weaknesses are absent.\n   <\/p>\n   <h3>\n    Does the same reasoning apply beyond student portals?\n   <\/h3>\n   <div class=\"nit-module-grid\">\n    <article class=\"nit-module-card\">\n     <div class=\"nit-module-card__head\">\n      <span class=\"nit-module-card__number\">\n       01\n      <\/span>\n      <h3>\n       Online shop\n      <\/h3>\n     <\/div>\n     <p>\n      A customer may read only their own delivery address. In a synthetic check, test whether one account can access another account\u2019s protected address.\n     <\/p>\n     <p class=\"nit-module-card__outcome\">\n      Testing question: does the server enforce the account\u2019s authorised role?\n     <\/p>\n    <\/article>\n    <article class=\"nit-module-card\">\n     <div class=\"nit-module-card__head\">\n      <span class=\"nit-module-card__number\">\n       02\n      <\/span>\n      <h3>\n       Salon booking\n      <\/h3>\n     <\/div>\n     <p>\n      Only authorised staff may change another customer\u2019s appointment. Test that ordinary customer roles cannot perform staff-only actions.\n     <\/p>\n     <p class=\"nit-module-card__outcome\">\n      Testing question: does the server enforce the account\u2019s authorised role?\n     <\/p>\n    <\/article>\n   <\/div>\n   <p>\n    On a\n    <strong>\n     fictional salon booking system\n    <\/strong>\n    , the rule may be: \u201cOnly authorised staff can change another customer\u2019s appointment.\u201d The tester checks that ordinary customer accounts cannot perform that staff-only action. These examples differ in purpose, but both start with a specific permission rule and end with evidence about whether that rule was enforced.\n   <\/p>\n  <\/section>\n  <section aria-labelledby=\"scanners-title\" id=\"scanners\">\n   <h2 id=\"scanners-title\">\n    Can a vulnerability scanner find everything?\n   <\/h2>\n   <p>\n    No. Automated scanning and human security testing solve different parts of the problem.\n   <\/p>\n   <div aria-label=\"Scrollable comparison table\" class=\"nit-pg-table-wrap\" role=\"region\" tabindex=\"0\">\n    <table class=\"nit-pg-table\">\n     <thead>\n      <tr>\n       <th scope=\"col\">\n        Technique\n       <\/th>\n       <th scope=\"col\">\n        What it is useful for\n       <\/th>\n       <th scope=\"col\">\n        Its boundary\n       <\/th>\n      <\/tr>\n     <\/thead>\n     <tbody>\n      <tr>\n       <th scope=\"row\">\n        <strong>\n         Passive scanning\n        <\/strong>\n       <\/th>\n       <td>\n        Reviews requests and responses already observed, such as headers or cookies\n       <\/td>\n       <td>\n        Cannot fully assess most business rules\n       <\/td>\n      <\/tr>\n      <tr>\n       <th scope=\"row\">\n        <strong>\n         Active scanning\n        <\/strong>\n       <\/th>\n       <td>\n        Sends new test requests to check for particular weakness patterns\n       <\/td>\n       <td>\n        Can change application state or cause disruption; needs specific permission\n       <\/td>\n      <\/tr>\n      <tr>\n       <th scope=\"row\">\n        <strong>\n         Manual verification\n        <\/strong>\n       <\/th>\n       <td>\n        Compares behaviour with real account, workflow and permission expectations\n       <\/td>\n       <td>\n        Depends on the tester\u2019s knowledge and the test cases chosen\n       <\/td>\n      <\/tr>\n      <tr>\n       <th scope=\"row\">\n        <strong>\n         Code\/component review\n        <\/strong>\n       <\/th>\n       <td>\n        Examines source code, dependencies or configuration when access is provided\n       <\/td>\n       <td>\n        Needs authorised access and an understanding of the deployed environment\n       <\/td>\n      <\/tr>\n     <\/tbody>\n    <\/table>\n   <\/div>\n   <p class=\"nit-pg-table-note\">\n    On a narrow screen, swipe horizontally to read all columns.\n   <\/p>\n   <p>\n    The\n    <a href=\"https:\/\/www.zaproxy.org\/docs\/desktop\/start\/features\/ascan\/\" rel=\"noopener noreferrer\" target=\"_blank\">\n     ZAP documentation on active scanning\n    <\/a>\n    <a aria-label=\"Reference 7\" href=\"#ref-7\">\n     [7]\n    <\/a>\n    makes two important points: active scans can put systems at risk, and automated checks cannot replace human analysis of application logic. Its\n    <a href=\"https:\/\/www.zaproxy.org\/docs\/desktop\/start\/features\/pscan\/\" rel=\"noopener noreferrer\" target=\"_blank\">\n     passive-scan documentation\n    <\/a>\n    <a aria-label=\"Reference 7\" href=\"#ref-7\">\n     [7]\n    <\/a>\n    explains a less intrusive form of inspection. \u201cPassive\u201d does not remove the requirement to follow the agreed assessment rules, and even apparently harmless requests can have unexpected effects on a fragile system.\n   <\/p>\n   <p>\n    The proper lesson is\n    <strong>\n     not\n    <\/strong>\n    \u201crun every available scanner.\u201d It is \u201cchoose a method appropriate to the security question, scope and system.\u201d\n   <\/p>\n   <p>\n    A\n    <strong>\n     vulnerability assessment\n    <\/strong>\n    commonly aims to identify and prioritise weaknesses across the agreed scope. A\n    <strong>\n     penetration test\n    <\/strong>\n    may go further by safely validating potential impact under explicit rules of engagement. Neither term authorises unrestricted activity, and neither method can guarantee that every flaw has been found.\n    <a href=\"https:\/\/nc4.go.ke\/organisations\/cii\/vapt\" rel=\"noopener noreferrer\" target=\"_blank\">\n     NC4\u2019s framework\n    <\/a>\n    <a aria-label=\"Reference 12\" href=\"#ref-12\">\n     [12]\n    <\/a>\n    describes their complementary purposes.\n   <\/p>\n   <p>\n    <strong>\n     Why this matters to a beginner:\n    <\/strong>\n    Suppose a scanner reports five outdated software packages. That is assessment evidence worth checking and prioritising. It is not permission to attempt to exploit them. A controlled demonstration of a specific weakness requires separate, suitable authorisation and a safe method. For our fictional portal, comparing an explicit permission rule with synthetic account behaviour is enough to demonstrate the lesson.\n   <\/p>\n  <\/section>\n  <section aria-labelledby=\"common-weaknesses-title\" class=\"nit-section-panel\" id=\"common-weaknesses\">\n   <h2 id=\"common-weaknesses-title\">\n    What kinds of website vulnerabilities do testers investigate?\n   <\/h2>\n   <p>\n    The\n    <a href=\"https:\/\/top10.owasp.org\/2025\/\" rel=\"noopener noreferrer\" target=\"_blank\">\n     OWASP Top 10:2025\n    <\/a>\n    <a aria-label=\"Reference 4\" href=\"#ref-4\">\n     [4]\n    <\/a>\n    identifies broad categories of web application security risk. It is an awareness resource, not a complete testing checklist. In the current release,\n    <strong>\n     A01 is Broken Access Control, A02 is Security Misconfiguration, A03 is Software Supply Chain Failures, A04 is Cryptographic Failures, A05 is Injection and A07 is Authentication Failures\n    <\/strong>\n    . Earlier editions use different category numbers and names.\n   <\/p>\n   <div aria-label=\"Scrollable comparison table\" class=\"nit-pg-table-wrap\" role=\"region\" tabindex=\"0\">\n    <table class=\"nit-pg-table\">\n     <thead>\n      <tr>\n       <th scope=\"col\">\n        Weakness or risk area\n       <\/th>\n       <th scope=\"col\">\n        Beginner example\n       <\/th>\n       <th scope=\"col\">\n        Main defensive idea\n       <\/th>\n      <\/tr>\n     <\/thead>\n     <tbody>\n      <tr>\n       <th scope=\"row\">\n        <strong>\n         Broken access control\n        <\/strong>\n       <\/th>\n       <td>\n        One student sees another student\u2019s private report\n       <\/td>\n       <td>\n        Check every relevant action and record on the server\n       <\/td>\n      <\/tr>\n      <tr>\n       <th scope=\"row\">\n        <strong>\n         Security misconfiguration\n        <\/strong>\n       <\/th>\n       <td>\n        Debug information is exposed on a public-facing page\n       <\/td>\n       <td>\n        Review deployment settings and remove unsafe defaults\n       <\/td>\n      <\/tr>\n      <tr>\n       <th scope=\"row\">\n        <strong>\n         Injection\n        <\/strong>\n       <\/th>\n       <td>\n        Untrusted input is combined unsafely with a database query\n       <\/td>\n       <td>\n        Use parameterised queries and safe APIs\n       <\/td>\n      <\/tr>\n      <tr>\n       <th scope=\"row\">\n        <strong>\n         Authentication or session weakness\n        <\/strong>\n       <\/th>\n       <td>\n        A session remains usable when it should no longer be valid\n       <\/td>\n       <td>\n        Apply appropriate login and session controls\n       <\/td>\n      <\/tr>\n      <tr>\n       <th scope=\"row\">\n        <strong>\n         Cross-site scripting (XSS)\n        <\/strong>\n       <\/th>\n       <td>\n        User-supplied text is displayed in a way that executes unintended browser script\n       <\/td>\n       <td>\n        Apply context-appropriate output encoding and safe browser APIs\n       <\/td>\n      <\/tr>\n      <tr>\n       <th scope=\"row\">\n        <strong>\n         Software supply-chain failure\n        <\/strong>\n       <\/th>\n       <td>\n        A compromised build component reaches the released application\n       <\/td>\n       <td>\n        Inventory components and protect the build and update process\n       <\/td>\n      <\/tr>\n      <tr>\n       <th scope=\"row\">\n        <strong>\n         Cryptographic failure\n        <\/strong>\n       <\/th>\n       <td>\n        Sensitive information is stored without suitable protection\n       <\/td>\n       <td>\n        Use established cryptographic protections correctly\n       <\/td>\n      <\/tr>\n     <\/tbody>\n    <\/table>\n   <\/div>\n   <p class=\"nit-pg-table-note\">\n    On a narrow screen, swipe horizontally to read all columns.\n   <\/p>\n   <p>\n    Do not use this table to label every discovered issue as \u201ccritical.\u201d Severity depends on the affected information, access conditions, realistic impact and the surrounding system. The same type of flaw can have very different consequences in two applications.\n   <\/p>\n  <\/section>\n  <section aria-labelledby=\"reports-title\" id=\"reports\">\n   <h2 id=\"reports-title\">\n    What should a useful vulnerability report contain?\n   <\/h2>\n   <p>\n    A security report is valuable when somebody responsible for the website can act on it. Kenya\u2019s\n    <a href=\"https:\/\/nc4.go.ke\/organisations\/cii\/vapt\" rel=\"noopener noreferrer\" target=\"_blank\">\n     National Computer and Cybercrimes Co-ordination Committee (NC4)\n    <\/a>\n    <a aria-label=\"Reference 12\" href=\"#ref-12\">\n     [12]\n    <\/a>\n    emphasises authorisation, evidence-based findings, prioritised remediation and retesting.\n   <\/p>\n   <p>\n    Here is a concise example from the\n    <strong>\n     fictional\n    <\/strong>\n    Lakeview classroom exercise:\n   <\/p>\n   <div aria-label=\"Scrollable comparison table\" class=\"nit-pg-table-wrap\" role=\"region\" tabindex=\"0\">\n    <table class=\"nit-pg-table\">\n     <thead>\n      <tr>\n       <th scope=\"col\">\n        Report field\n       <\/th>\n       <th scope=\"col\">\n        Example entry\n       <\/th>\n      <\/tr>\n     <\/thead>\n     <tbody>\n      <tr>\n       <th scope=\"row\">\n        <strong>\n         Title\n        <\/strong>\n       <\/th>\n       <td>\n        Missing report-ownership check\n       <\/td>\n      <\/tr>\n      <tr>\n       <th scope=\"row\">\n        <strong>\n         Scope\n        <\/strong>\n       <\/th>\n       <td>\n        Local training portal; approved synthetic accounts\n       <\/td>\n      <\/tr>\n      <tr>\n       <th scope=\"row\">\n        <strong>\n         Expected\n        <\/strong>\n       <\/th>\n       <td>\n        Brian cannot read Amina\u2019s report\n       <\/td>\n      <\/tr>\n      <tr>\n       <th scope=\"row\">\n        <strong>\n         Observed\n        <\/strong>\n       <\/th>\n       <td>\n        Brian\u2019s test session received Amina\u2019s synthetic report\n       <\/td>\n      <\/tr>\n      <tr>\n       <th scope=\"row\">\n        <strong>\n         Evidence\n        <\/strong>\n       <\/th>\n       <td>\n        Redacted lab screenshot, account roles and test-case record\n       <\/td>\n      <\/tr>\n      <tr>\n       <th scope=\"row\">\n        <strong>\n         Likely cause\n        <\/strong>\n       <\/th>\n       <td>\n        Server checks login but not resource ownership\n       <\/td>\n      <\/tr>\n      <tr>\n       <th scope=\"row\">\n        <strong>\n         Impact\n        <\/strong>\n       <\/th>\n       <td>\n        In a real deployment, unauthorised disclosure of private results\n       <\/td>\n      <\/tr>\n      <tr>\n       <th scope=\"row\">\n        <strong>\n         Recommended fix\n        <\/strong>\n       <\/th>\n       <td>\n        Apply server-side ownership checks to report retrieval and related operations\n       <\/td>\n      <\/tr>\n      <tr>\n       <th scope=\"row\">\n        <strong>\n         Retest\n        <\/strong>\n       <\/th>\n       <td>\n        All five authorised access cases pass after correction\n       <\/td>\n      <\/tr>\n     <\/tbody>\n    <\/table>\n   <\/div>\n   <p class=\"nit-pg-table-note\">\n    On a narrow screen, swipe horizontally to read all columns.\n   <\/p>\n   <p>\n    A useful report also identifies who owns the fix and how it will be verified. Keep proof minimal: the affected function, the expected rule, the specific observation and enough synthetic or redacted evidence to reproduce it. Do not collect real private records or publish account secrets as \u201cproof.\u201d\n   <\/p>\n   <h3>\n    Which finding should be fixed first?\n   <\/h3>\n   <p>\n    A report should help the owner prioritise, not just collect warnings. Consider\n    <strong>\n     sensitivity of the exposed data\n    <\/strong>\n    ,\n    <strong>\n     who can reach the affected function\n    <\/strong>\n    ,\n    <strong>\n     how reliably the issue can be reproduced\n    <\/strong>\n    ,\n    <strong>\n     realistic impact\n    <\/strong>\n    , and\n    <strong>\n     existing protections\n    <\/strong>\n    . In the fictional school portal, a confirmed ability to retrieve another student&#8217;s private report deserves prompt attention. A missing optional hardening header or an unverified version alert requires a different assessment; the correct priority cannot be assigned from the scanner label alone. NC4&#8217;s framework likewise emphasises real risk, exposure and exploitability rather than raw finding counts.\n   <\/p>\n   <p>\n    A successful retest means the\n    <em>\n     tested issue\n    <\/em>\n    was corrected under\n    <em>\n     tested conditions\n    <\/em>\n    . It is not a certificate that the entire website is invulnerable.\n   <\/p>\n  <\/section>\n  <section aria-labelledby=\"practice-title\" class=\"nit-section-panel\" id=\"practice\">\n   <h2 id=\"practice-title\">\n    How can a beginner practise safely?\n   <\/h2>\n   <p>\n    Start with an exercise that requires\n    <strong>\n     reasoning before tools\n    <\/strong>\n    . Draw a small website with three roles\u2014visitor, student and administrator. Write down what each role may read or change. Then design one allowed and one denied test for each sensitive function. If you cannot explain the expected permission, a scanner will not fix that gap in understanding.\n   <\/p>\n   <p>\n    Next, use an intentionally vulnerable teaching environment prepared for learning.\n    <a href=\"https:\/\/owasp.org\/projects\/juice-shop\" rel=\"noopener noreferrer\" target=\"_blank\">\n     OWASP Juice Shop\n    <\/a>\n    <a aria-label=\"Reference 8\" href=\"#ref-8\">\n     [8]\n    <\/a>\n    is a deliberately insecure training application; it should be used only in its permitted learning deployment or an isolated local setup you control. A browser\u2019s developer tools can help you understand your own lab requests and responses.\n    <a href=\"https:\/\/www.zaproxy.org\/\" target=\"_blank\" rel=\"noopener\">\n     OWASP ZAP\n    <\/a>\n    can help learners inspect traffic and understand alerts within a properly authorised scope.\n   <\/p>\n   <p>\n    <strong>\n     Try this paper-based five-minute exercise:\n    <\/strong>\n    a student can view their own marks, edit their contact telephone number, and download fee receipts. For each function, write a rule saying\n    <em>\n     whose\n    <\/em>\n    records may be accessed, whether a signed-out visitor may use the function, and what evidence would demonstrate denial. This gives you an assessment plan before you install anything.\n   <\/p>\n   <p>\n    <strong>\n     Check your reasoning:\n    <\/strong>\n    (1) Each student may read only their own marks and receipts. (2) Only the signed-in account may change its own contact number, unless a separate authorised staff workflow applies. (3) A signed-out visitor is denied these private operations. (4) A convincing test record shows the account role, the synthetic resource, the expected outcome and the observed result. If the rule is unclear, ask the system owner to define it before testing.\n   <\/p>\n   <p>\n    If you want a collection of projects with deliverables, NIT\u2019s\n    <a href=\"https:\/\/niteducation.com\/resources\/cybersecurity-projects-for-beginners\/\">\n     Cybersecurity Projects for Beginners\n    <\/a>\n    covers that separate learning objective. This article focuses on\n    <em>\n     how the discovery and evidence process works\n    <\/em>\n    .\n   <\/p>\n  <\/section>\n  <section aria-labelledby=\"kenya-law-title\" id=\"kenya-law\">\n   <h2 id=\"kenya-law-title\">\n    Is ethical website security testing legal in Kenya?\n   <\/h2>\n   <p>\n    Permission and scope are essential. Kenya\u2019s\n    <a href=\"https:\/\/new.kenyalaw.org\/akn\/ke\/act\/2018\/5\/eng@2025-11-04\/source\" rel=\"noopener noreferrer\" target=\"_blank\">\n     Computer Misuse and Cybercrimes Act, Cap. 79C\n    <\/a>\n    <a aria-label=\"Reference 13\" href=\"#ref-13\">\n     [13]\n    <\/a>\n    , including Section 14 on unauthorised access, provides relevant legal context; Because laws and court interpretations can change, check the current applicable legislation before drawing conclusions about a particular proposed test. The\n    <a href=\"https:\/\/nc4.go.ke\/organisations\/cii\/vapt\" rel=\"noopener noreferrer\" target=\"_blank\">\n     NC4 vulnerability-assessment framework\n    <\/a>\n    <a aria-label=\"Reference 12\" href=\"#ref-12\">\n     [12]\n    <\/a>\n    specifically calls for written authorisation, agreed objectives, defined scope and rules of engagement.\n   <\/p>\n   <p>\n    For a beginner, the practical boundary is clear:\n    <strong>\n     a website being publicly reachable does not give you permission to probe it\n    <\/strong>\n    . Use a controlled training application or an assessment expressly approved by someone authorised to grant that permission. Know which accounts, systems and methods are included. Stop if your actions may expose real records or affect an excluded service.\n   <\/p>\n   <p>\n    If you unexpectedly notice what seems to be a serious weakness, do not keep exploring other people\u2019s information. Preserve only minimal safe details and report privately through the website owner&#8217;s designated security channel or published disclosure policy.\n    <a href=\"https:\/\/cheatsheetseries.owasp.org\/cheatsheets\/Vulnerability_Disclosure_Cheat_Sheet.html\" rel=\"noopener noreferrer\" target=\"_blank\">\n     OWASP&#8217;s Vulnerability Disclosure guidance\n    <\/a>\n    <a aria-label=\"Reference 11\" href=\"#ref-11\">\n     [11]\n    <\/a>\n    explains how to report clearly while respecting privacy. Specific legal questions should be resolved against the current law and the facts of the proposed activity.\n   <\/p>\n  <\/section>\n  <section aria-labelledby=\"mistakes-title\" id=\"mistakes\">\n   <h2 id=\"mistakes-title\">\n    Common mistakes that lead to poor findings\n   <\/h2>\n   <p>\n    <strong>\n     Mistake: treating a scanner alert as a confirmed exploit.\n    <\/strong>\n    Better: state exactly what was observed, check applicability, and qualify any unverified claim.\n   <\/p>\n   <p>\n    <strong>\n     Mistake: checking the login page but not the resource permission.\n    <\/strong>\n    Better: document both authentication and authorisation rules. A signed-in account may still be barred from a particular action.\n   <\/p>\n   <p>\n    <strong>\n     Mistake: making a fix that blocks legitimate users.\n    <\/strong>\n    Better: retest both permitted and prohibited actions, as the Lakeview matrix demonstrates.\n   <\/p>\n   <p>\n    <strong>\n     Mistake: focusing only on the visible page.\n    <\/strong>\n    Better: understand the server, its APIs, sessions, configuration and other approved components.\n   <\/p>\n   <p>\n    <strong>\n     Mistake: saving unnecessary private information.\n    <\/strong>\n    Better: use synthetic records, redact evidence and share reports only with the responsible team.\n   <\/p>\n  <\/section>\n  <section aria-labelledby=\"faq-title\" class=\"nit-section-panel\" id=\"faq\">\n   <h2 id=\"faq-title\">\n    Frequently asked questions\n   <\/h2>\n   <div class=\"nit-faq\">\n    <details class=\"nit-faq__item\">\n     <summary>\n      How do hackers know which websites might have vulnerabilities?\n     <\/summary>\n     <div class=\"nit-faq__answer\">\n      <p>\n       They examine the systems and functionality within their authorised scope, look for known risk patterns and investigate unusual security behaviour. A possible clue does not establish a real weakness until its meaning is checked.\n      <\/p>\n     <\/div>\n    <\/details>\n    <details class=\"nit-faq__item\">\n     <summary>\n      Can a normal-looking website still be insecure?\n     <\/summary>\n     <div class=\"nit-faq__answer\">\n      <p>\n       Yes. The problem may be in server-side permissions or application logic that is invisible to an ordinary visitor. A polished interface is not a substitute for tested security controls.\n      <\/p>\n     <\/div>\n    <\/details>\n    <details class=\"nit-faq__item\">\n     <summary>\n      Does HTTPS mean a website is secure?\n     <\/summary>\n     <div class=\"nit-faq__answer\">\n      <p>\n       No. HTTPS helps protect data in transit, but it does not prove that accounts have the right permissions or that application code and settings are free of weaknesses.\n      <\/p>\n     <\/div>\n    <\/details>\n    <details class=\"nit-faq__item\">\n     <summary>\n      Can a scanner tell me whether a website is safe?\n     <\/summary>\n     <div class=\"nit-faq__answer\">\n      <p>\n       Not conclusively. Scanners check particular patterns. They can miss business-logic problems, and alerts require interpretation. An assessment\u2019s conclusion must reflect its scope and evidence.\n      <\/p>\n     <\/div>\n    <\/details>\n    <details class=\"nit-faq__item\">\n     <summary>\n      Must a beginner learn programming first?\n     <\/summary>\n     <div class=\"nit-faq__answer\">\n      <p>\n       Not before learning the basic method. Start with HTTP, login sessions, roles and access rules. Programming becomes increasingly helpful when reading code, building test applications and understanding fixes.\n      <\/p>\n     <\/div>\n    <\/details>\n    <details class=\"nit-faq__item\">\n     <summary>\n      Can I use someone else\u2019s school or business website for practice?\n     <\/summary>\n     <div class=\"nit-faq__answer\">\n      <p>\n       Not without valid authorisation for the specific assessment. Use an isolated lab or a training environment that permits those exercises.\n      <\/p>\n     <\/div>\n    <\/details>\n    <details class=\"nit-faq__item\">\n     <summary>\n      What happens after a vulnerability is reported?\n     <\/summary>\n     <div class=\"nit-faq__answer\">\n      <p>\n       The responsible team evaluates the finding, addresses its root cause and arranges an appropriate retest. The tester records the retest result and any remaining limitations.\n      <\/p>\n     <\/div>\n    <\/details>\n   <\/div>\n  <\/section>\n  <section aria-labelledby=\"lesson-title\" id=\"lesson\">\n   <h2 id=\"lesson-title\">\n    The lesson to remember\n   <\/h2>\n   <p>\n    A responsible tester does not begin by trying random attacks. They begin with an expectation:\n    <em>\n     \u201cBrian must not be able to read Amina\u2019s report.\u201d\n    <\/em>\n    They gather authorised evidence, decide whether that expectation failed, explain the risk and check the correction. This disciplined approach applies to online shops, booking systems, student portals and many other web applications.\n   <\/p>\n   <p>\n    For details about the NIT study pathway, see the official\n    <a href=\"https:\/\/niteducation.com\/resources\/cybersecurity-course-in-kenya\/\" rel=\"noopener noreferrer\" target=\"_blank\">\n     Cybersecurity Course in Kenya\n    <\/a>\n    <a aria-label=\"Reference 15\" href=\"#ref-15\">\n     [15]\n    <\/a>\n    .\n   <\/p>\n   <p>\n    To compare the career roles rather than the website-testing method, see\n    <a href=\"https:\/\/niteducation.com\/resources\/cybersecurity-analyst-vs-ethical-hacker\/\">\n     Cybersecurity Analyst vs Ethical Hacker\n    <\/a>\n    .\n   <\/p>\n  <\/section>\n  <section aria-labelledby=\"register-heading\" class=\"nit-pg-enrol\" id=\"register\">\n   <div class=\"nit-pg-enrol__copy\">\n    <p class=\"nit-pg-eyebrow\">\n     Learn to test responsibly\n    <\/p>\n    <h2 id=\"register-heading\">\n     Learn cybersecurity at Newton Institute of Technology\n    <\/h2>\n    <p>\n     At Newton Institute of Technology in Migori Town, Kenya, students explore computer systems, networking, Linux, authorised testing, security monitoring and technical reporting through structured learning.\n    <\/p>\n    <p>\n     The published cybersecurity pathway includes six months of institutional training followed by three months of compulsory industrial attachment. Confirm current study arrangements with Admissions.\n    <\/p>\n   <\/div>\n   <div aria-label=\"NIT cybersecurity programme at a glance\" class=\"nit-pg-enrol__details\">\n    <p>\n     <span>\n      Institutional training\n     <\/span>\n     <strong>\n      6 months\n     <\/strong>\n    <\/p>\n    <p>\n     <span>\n      Industrial attachment\n     <\/span>\n     <strong>\n      3 months\n     <\/strong>\n    <\/p>\n    <p>\n     <span>\n      Location\n     <\/span>\n     <strong>\n      Migori Town, Kenya\n     <\/strong>\n    <\/p>\n    <p>\n     <span>\n      Call \/ WhatsApp\n     <\/span>\n     <strong>\n      <a href=\"tel:+254713584858\">\n       +254 713 584 858\n      <\/a>\n     <\/strong>\n    <\/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\/\">\n     Register for cybersecurity training\n    <\/a>\n    <a class=\"nit-pg-button nit-pg-button--outline\" href=\"https:\/\/niteducation.com\/resources\/cybersecurity-course-in-kenya\/\">\n     See cybersecurity course details\n    <\/a>\n    <a class=\"nit-pg-button nit-pg-button--outline\" href=\"https:\/\/wa.me\/254713584858?text=Hello%20NIT%2C%20I%20would%20like%20to%20learn%20about%20the%20Cybersecurity%20course.\" target=\"_blank\" rel=\"noopener\">\n     Ask Admissions on WhatsApp\n    <\/a>\n   <\/div>\n  <\/section>\n  <section aria-labelledby=\"references-title\" class=\"nit-sources\" id=\"references\">\n   <h2 id=\"references-title\">\n    Sources and references\n   <\/h2>\n   <ol>\n    <li id=\"ref-1\">\n     <a href=\"https:\/\/wstg.owasp.org\/v4.2\/4-Web_Application_Security_Testing\/\" rel=\"noopener noreferrer\" target=\"_blank\">\n      OWASP Web Security Testing Guide \u2014 stable web application testing chapters\n     <\/a>\n     . Technical testing categories; current hosted stable guide.\n    <\/li>\n    <li id=\"ref-2\">\n     <a href=\"https:\/\/wstg.owasp.org\/latest\/4-Web_Application_Security_Testing\/01-Information_Gathering\/00-Information_Gathering_Overview\/\" rel=\"noopener noreferrer\" target=\"_blank\">\n      OWASP Web Security Testing Guide \u2014 information gathering, latest development edition\n     <\/a>\n     . Attack-surface discovery and scope.\n    <\/li>\n    <li id=\"ref-3\">\n     <a href=\"https:\/\/wstg.owasp.org\/latest\/3-The_OWASP_Testing_Framework\/0-The_Web_Security_Testing_Framework\/\" rel=\"noopener noreferrer\" target=\"_blank\">\n      OWASP Web Security Testing Guide \u2014 testing framework, latest development edition\n     <\/a>\n     . Flexible testing activity model.\n    <\/li>\n    <li id=\"ref-4\">\n     <a href=\"https:\/\/top10.owasp.org\/2025\/\" rel=\"noopener noreferrer\" target=\"_blank\">\n      OWASP Top 10:2025\n     <\/a>\n     . Current published category list and awareness framework.\n    <\/li>\n    <li id=\"ref-5\">\n     <a href=\"https:\/\/top10.owasp.org\/2025\/A01_2025-Broken_Access_Control\/\" rel=\"noopener noreferrer\" target=\"_blank\">\n      OWASP Top 10:2025 \u2014 Broken Access Control\n     <\/a>\n     . Server-side access enforcement guidance.\n    <\/li>\n    <li id=\"ref-6\">\n     <a href=\"https:\/\/developer.mozilla.org\/en-US\/docs\/Web\/HTTP\/Guides\/Overview\" rel=\"noopener noreferrer\" target=\"_blank\">\n      MDN \u2014 Overview of HTTP\n     <\/a>\n     . Requests and responses.\n    <\/li>\n    <li id=\"ref-7\">\n     <a href=\"https:\/\/www.zaproxy.org\/docs\/desktop\/start\/features\/ascan\/\" rel=\"noopener noreferrer\" target=\"_blank\">\n      ZAP \u2014 Active Scan\n     <\/a>\n     and\n     <a href=\"https:\/\/www.zaproxy.org\/docs\/desktop\/start\/features\/pscan\/\" rel=\"noopener noreferrer\" target=\"_blank\">\n      Passive Scan\n     <\/a>\n     . Scanning methods and limitations.\n    <\/li>\n    <li id=\"ref-8\">\n     <a href=\"https:\/\/owasp.org\/projects\/juice-shop\" rel=\"noopener noreferrer\" target=\"_blank\">\n      OWASP Juice Shop\n     <\/a>\n     . Deliberately vulnerable training application.\n    <\/li>\n    <li id=\"ref-9\">\n     <a href=\"https:\/\/asvs.owasp.org\/\" rel=\"noopener noreferrer\" target=\"_blank\">\n      OWASP Application Security Verification Standard 5.0.0\n     <\/a>\n     . Stable application-control verification requirements (released 30 May 2025).\n    <\/li>\n    <li id=\"ref-10\">\n     <a href=\"https:\/\/cheatsheetseries.owasp.org\/cheatsheets\/Authorization_Cheat_Sheet.html\" rel=\"noopener noreferrer\" target=\"_blank\">\n      OWASP Authorisation Cheat Sheet\n     <\/a>\n     . Deny-by-default and trusted-side access checks.\n    <\/li>\n    <li id=\"ref-11\">\n     <a href=\"https:\/\/cheatsheetseries.owasp.org\/cheatsheets\/Vulnerability_Disclosure_Cheat_Sheet.html\" rel=\"noopener noreferrer\" target=\"_blank\">\n      OWASP Vulnerability Disclosure Cheat Sheet\n     <\/a>\n     . Private reporting and evidence handling.\n    <\/li>\n    <li id=\"ref-12\">\n     <a href=\"https:\/\/nc4.go.ke\/organisations\/cii\/vapt\" rel=\"noopener noreferrer\" target=\"_blank\">\n      NC4 Kenya \u2014 Vulnerability Assessment Framework\n     <\/a>\n     . Written authorisation, scope, reporting, remediation and retesting.\n    <\/li>\n    <li id=\"ref-13\">\n     <a href=\"https:\/\/new.kenyalaw.org\/akn\/ke\/act\/2018\/5\/eng@2025-11-04\/source\" rel=\"noopener noreferrer\" target=\"_blank\">\n      Kenya Law \u2014 Computer Misuse and Cybercrimes Act, Cap. 79C, consolidated 4 November 2025\n     <\/a>\n     ;\n     <a href=\"https:\/\/www.parliament.go.ke\/sites\/default\/files\/2025-10\/Computer%20Misuse%20and%20Cybercrimes%20%28Amendment%29%20Act%2C%202025.pdf\" rel=\"noopener noreferrer\" target=\"_blank\">\n      Parliament of Kenya \u2014 Amendment Act No. 17 of 2025\n     <\/a>\n     .\n    <\/li>\n    <li id=\"ref-14\">\n     <a href=\"https:\/\/datatracker.ietf.org\/doc\/html\/rfc6761#section-6.5\" rel=\"noopener noreferrer\" target=\"_blank\">\n      IETF RFC 6761 \u2014 Special-Use Domain Names\n     <\/a>\n     . Reserved\n     <code>\n      .example\n     <\/code>\n     documentation names.\n    <\/li>\n    <li id=\"ref-15\">\n     <a href=\"https:\/\/niteducation.com\/resources\/cybersecurity-course-in-kenya\/\" rel=\"noopener noreferrer\" target=\"_blank\">\n      Newton Institute of Technology \u2014 Cybersecurity Course in Kenya\n     <\/a>\n     and\n     <a href=\"https:\/\/niteducation.com\/admissions\/\" rel=\"noopener noreferrer\" target=\"_blank\">\n      Admissions\n     <\/a>\n     . Institutional programme and contact information.\n    <\/li>\n   <\/ol>\n   <p>\n    Sources reviewed 12 November 2026 \u00b7 Editorial responsibility: Newton Institute of Technology Editorial Team.\n   <\/p>\n  <\/section>\n <\/div>\n<\/article>\n","protected":false},"excerpt":{"rendered":"<p>CYBERSECURITY EXPLAINED Beginner website security guide How Do Ethical Hackers Find Website Vulnerabilities? A Beginner&#8217;s Guide AUTHORISE \u2192 MAP \u2192 VERIFY \u2192 REPORT \u2192 RETEST How ethical hackers trace a possible website weakness from the first clue to reliable evidence, a clear report and a retested fix\u2014with a fictional student portal and safe examples. Understand [&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":[844,845,846],"class_list":["post-3827","post","type-post","status-publish","format-standard","hentry","category-ict","tag-how-do-ethical-hackers-find-website-vulnerabilities","tag-how-do-hackers-find-website-vulnerabilities","tag-website-security-testing"],"_links":{"self":[{"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/posts\/3827","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=3827"}],"version-history":[{"count":2,"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/posts\/3827\/revisions"}],"predecessor-version":[{"id":3871,"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/posts\/3827\/revisions\/3871"}],"wp:attachment":[{"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/media?parent=3827"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/categories?post=3827"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/tags?post=3827"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}