diff --git a/.idea/.gitignore b/.idea/.gitignore new file mode 100644 index 0000000..26d3352 --- /dev/null +++ b/.idea/.gitignore @@ -0,0 +1,3 @@ +# Default ignored files +/shelf/ +/workspace.xml diff --git a/.idea/Good_First_Issue_Web_App.iml b/.idea/Good_First_Issue_Web_App.iml new file mode 100644 index 0000000..d0876a7 --- /dev/null +++ b/.idea/Good_First_Issue_Web_App.iml @@ -0,0 +1,8 @@ + + + + + + + + \ No newline at end of file diff --git a/.idea/inspectionProfiles/Project_Default.xml b/.idea/inspectionProfiles/Project_Default.xml new file mode 100644 index 0000000..4dfb542 --- /dev/null +++ b/.idea/inspectionProfiles/Project_Default.xml @@ -0,0 +1,21 @@ + + + + \ No newline at end of file diff --git a/.idea/inspectionProfiles/profiles_settings.xml b/.idea/inspectionProfiles/profiles_settings.xml new file mode 100644 index 0000000..105ce2d --- /dev/null +++ b/.idea/inspectionProfiles/profiles_settings.xml @@ -0,0 +1,6 @@ + + + + \ No newline at end of file diff --git a/.idea/modules.xml b/.idea/modules.xml new file mode 100644 index 0000000..b29f58e --- /dev/null +++ b/.idea/modules.xml @@ -0,0 +1,8 @@ + + + + + + + + \ No newline at end of file diff --git a/.idea/vcs.xml b/.idea/vcs.xml new file mode 100644 index 0000000..35eb1dd --- /dev/null +++ b/.idea/vcs.xml @@ -0,0 +1,6 @@ + + + + + + \ No newline at end of file diff --git a/frontend/src/App.js b/frontend/src/App.js index 4f2ede4..0e476ea 100644 --- a/frontend/src/App.js +++ b/frontend/src/App.js @@ -1,6 +1,10 @@ import "./App.css"; import {Hero, About, Repositories, Form, Layout} from './pages' import { Route, RouterProvider, createBrowserRouter, createRoutesFromElements } from 'react-router-dom' +import IncidentResponse from "./pages/IncidentResponse"; + +// inside or equivalent +} /> const router = createBrowserRouter( createRoutesFromElements( diff --git a/frontend/src/pages/Navbar.js b/frontend/src/pages/Navbar.js index aa535c8..051a94e 100644 --- a/frontend/src/pages/Navbar.js +++ b/frontend/src/pages/Navbar.js @@ -27,6 +27,8 @@ function Navbar() { Form + Incident Response Plan +
    diff --git a/frontend/src/pages/incident-response.html b/frontend/src/pages/incident-response.html new file mode 100644 index 0000000..30d367f --- /dev/null +++ b/frontend/src/pages/incident-response.html @@ -0,0 +1,29 @@ + + + + + + Incident Response Plan + + + + + +
    +

    Incident Response Plan

    +

    Creating an incident response plan is crucial for organizations for several reasons:

    +
      +
    • Minimize Impact and Damage: React quickly and effectively to security incidents.
      • +
    • Clear Roles and Responsibilities: Everyone knows their role during a crisis.
      • +
    • Enhance Communication: Ensure accurate and consistent information is shared.
      • +
    • Compliance: Meet regulatory and legal requirements.
      • +
    • Reputation: Preserve trust with customers and stakeholders.
      • +
    • Cost Savings: Prevent unnecessary expenses due to poor response.
      • +
    • Continuous Improvement: Learn and adapt after incidents.
      • +
    +
    + + diff --git a/frontend/src/pages/incidentResponse.js b/frontend/src/pages/incidentResponse.js new file mode 100644 index 0000000..a83f671 --- /dev/null +++ b/frontend/src/pages/incidentResponse.js @@ -0,0 +1,30 @@ +import React from "react"; + +const IncidentResponse = () => { + return ( +
    +

    Incident Response Plan

    +

    Creating an incident response plan is crucial for organizations for several reasons:

    +
      +
    • Minimize Impact and Damage: React quickly and effectively to limit damage and shorten recovery time.
      • +
    • Clear Roles and Responsibilities: Defines responsibilities for the response team, avoiding confusion.
      • +
    • Enhance Communication: Provides internal and external communication protocols.
      • +
    • Legal and Regulatory Compliance: Ensures compliance with laws and avoids fines.
      • +
    • Preserve Organizational Reputation: A transparent and fast response builds trust.
      • +
    • Reduction in Downtime: Predetermined steps reduce downtime and business impact.
      • +
    • Cost Savings: Prevents unnecessary expenses from misinformation or chaos.
      • +
    • Continuous Improvement: Post-incident reviews refine procedures.
      • +
    • Stakeholder Assurance: Shows partners and customers the org is prepared.
      • +
    • Enhanced Security Posture: Regular reviews help identify and fix gaps.
      • +
    +

    + + In essence, an incident response plan is like an insurance policy for cybersecurity incidents. + You hope never to use it, but when the need arises, you’ll be glad you have it. + +

    +
    + ); +}; + +export default IncidentResponse;