Module 1 of 20 — Foundations

Foundations of Cybersecurity & Security Mindset

Cybersecurity is not just about tools and technologies it is a mindset. Before you can defend systems, you must learn to think like an attacker. Before you can secure data, you must understand why it is valuable and how it can be exploited. This module introduces the mental frameworks, core security principles, and foundational concepts that serve as the backbone of every topic in this curriculum.

The CIA Triad: Cornerstone of Security

Every security control, policy, and technology exists to uphold one or more of the three pillars: Confidentiality, Integrity, Availability. Understanding these principles is non-negotiable for any security professional.

Confidentiality

Ensuring that data is accessible only to those authorized to view it. Achieved through encryption, access controls, and data classification. Analogy: A sealed letter that only the intended recipient can open.

Real Incident: Equifax breach (2017): Unencrypted personal data of 147 million people exposed due to poor access controls and unpatched vulnerabilities.

Integrity

Maintaining the accuracy and completeness of data. Prevents unauthorized modification. Mechanisms include hashing, digital signatures, and checksums. Analogy: A tamper-evident seal on a medicine bottle.

Real Incident: Stuxnet (2010): Malware compromised industrial system integrity by altered centrifuge speeds while showing normal readings to operators.

Availability

Ensuring systems and data are accessible when needed. Involves redundancy, DDoS mitigation, backups, and disaster recovery planning. Analogy: A 24/7 always-on hospital emergency room.

Real Incident: Dyn DDoS attack (2016): Major websites (Twitter, Netflix, Reddit) unavailable for hours when Mirai botnet overwhelmed DNS provider Dyn.

Security Mindset Principles

Tools change. Technologies evolve. But the security mindset—a way of thinking about risk, trust, and adversary behavior—remains constant. These five mental models guide every decision you make as a security professional.

1

Assume Breach

Operate under the assumption that systems are already compromised. Focus on rapid detection and response rather than purely preventive measures.

Warning

Case Study: Target (2013): Attackers had network access for 3 weeks before detection. Assume-breach approach would have triggered alerts earlier through anomaly detection.
2

Least Privilege

Grant only the minimum permissions necessary for a user or system to perform its function. No one should have more access than absolutely required.

Warning

Case Study: SolarWinds (2020): Compromised Orion update mechanism gave attackers elevated access across 18,000 organizations due to excessive trust in update signing.
3

Defense in Depth

Multiple overlapping security controls so that if one fails, others still protect the asset. Like layers of an onion—each layer must be breached.

Warning

Case Study: Colonial Pipeline (2021): Single compromised password led to operational shutdown. Multi-factor authentication at all critical access points would have prevented full compromise.
4

Zero Trust

Never trust, always verify. Authenticate and authorize every access request regardless of origin. Trust is earned continuously, not granted permanently.

Warning

Case Study: Okta (2022): Social engineering of support staff led to breach. Zero Trust MFA for all administrative actions would have limited lateral movement.
5

Threat Modeling

Systematically identify threats, vulnerabilities, and mitigations before building systems. Ask: What can go wrong? How likely? How bad?

Warning

Case Study: Log4Shell (2021): Lack of threat modeling around remote code execution in logging framework led to global crisis affecting millions of Java applications.

Understanding Attack Vectors

Attackers do not simply hack systems they exploit weaknesses. These weaknesses may exist in software, networks, configurations, or even human behavior. By understanding common attack vectors, you can better identify where vulnerabilities exist and where defensive measures must be implemented to protect systems, data, and users.

Network Attacks

Common Techniques:

  • Man-in-the-middle (MITM)
  • Denial of Service (DoS/DDoS)
  • Port scanning & enumeration
  • Packet sniffing

Defensive Measures:

Firewalls, IDS/IPS, VPN encryption, network segmentation

Application Attacks

Common Techniques:

  • SQL Injection
  • Cross-Site Scripting (XSS)
  • Cross-Site Request Forgery (CSRF)
  • Remote Code Execution (RCE)

Defensive Measures:

Input validation, parameterized queries, Content Security Policy (CSP), secure coding practices

Social Engineering

Common Techniques:

  • Phishing emails
  • Pretexting calls
  • Tailgating physical access
  • Baiting with USB drops

Defensive Measures:

Security awareness training, MFA, physical security controls, verification procedures

Supply Chain

Common Techniques:

  • Compromised software updates
  • Dependency vulnerabilities
  • Hardware backdoors
  • Third-party breaches

Defensive Measures:

Software Bill of Materials (SBOM), code signing verification, vendor risk assessments, network segmentation

Current Threat Landscape & Trends

The cyber threat landscape evolves rapidly. Understanding trends helps you anticipate attacks before they hit your organization.

AI-Powered Attacks

Attackers use machine learning for automated phishing, deepfakes for social engineering, and adaptive malware that evades detection.

Impact:

Traditional signature-based defenses struggle against AI-generated polymorphic malware.

Defensive Approach:

AI-powered defenses, behavioral analysis, and employee training on deepfake recognition.

Ransomware-as-a-Service (RaaS)

Ransomware kits available on dark markets with affiliate programs, customer support, and profit-sharing models.

Impact:

Lower barrier to entry for criminals means more frequent, sophisticated attacks across all sectors.

Defensive Approach:

Immutable backups, EDR solutions, network segmentation, and user behavior analytics.

Living Off the Land (LotL)

Attackers use legitimate system tools and processes (PowerShell, WMI, certutil) instead of malware to evade detection.

Impact:

Traditional antivirus misses these attacks because no malicious binaries are dropped.

Defensive Approach:

Detailed logging, monitoring for anomalous tool usage, application whitelisting, and behavioral rules.

Security as a Continuous Process

Security is not a product you buy it is a process you maintain. The NIST Cybersecurity Framework outlines five core functions that form a continuous cycle.

NIST Cybersecurity Framework (Identify, Protect, Detect, Respond, Recover)

1Identify

Develop organizational understanding to manage cybersecurity risk.

2Protect

Implement safeguards to ensure delivery of critical services.

3Detect

Develop capabilities to identify cybersecurity events.

4Respond

Take actions regarding detected incidents.

5Recover

Maintain resilience and restore capabilities after incidents.

Key Takeaways

  • CIA Triad is the foundation—every security control maps to at least one pillar.
  • Security mindset means thinking like an attacker while acting as a defender.
  • Defense in depth ensures no single point of failure compromises security.
  • Assume breach acknowledges that determined attackers will eventually get in.
  • Least privilege limits damage when credentials are compromised.
  • Real incidents referenced throughout illustrate why these principles matter.

Further Reading & Resources

NIST Cybersecurity Framework

Official NIST.gov framework documentation and guidelines.

CIS Controls

Critical Security Controls prioritized by the Center for Internet Security.

MITRE ATT&CK

Global knowledge base of adversary tactics and techniques.

OWASP Top 10

Most critical web application security risks.