LECTURE #15

Topic 1: Introduction to SDLC and DevSecOps

Concept:

Understanding the basics of how software is made and the difference between the old way and
the new secure way.

Simple Explanation:

 What is SDLC? SDLC stands for Software Development Life Cycle. It is simply the process
used to design, develop, and test software1.
 The Old Problem: In the past, people only checked for security issues at the very end of the
project. This was a big mistake because it left security as an afterthought2.
 The Solution (DevSecOps): The solution is DevSecOps. This means adding security steps at
every single stage of making the software, not just the end3.

Real-Life Example:

Imagine building a house. If you build the whole house and forget to put locks on the doors until
the very end, it is hard to fix. DevSecOps is like planning the locks and security cameras before
and during construction4.

Topic 2: What is DevSecOps? (Definition & Core Concept)

Concept:

Defining DevSecOps and understanding who is responsible for security.

Simple Explanation:

 Definition: The word DevSecOps is a combination of three things: Development + Security +

Operations5.
 Core Concept: The main idea is that security is not just one team's job. Everyone involved in
the project is responsible for security6.
 The Motto: The famous saying for DevSecOps is: "Security is code, and code is everyone's
responsibility"7.

Topic 3: The 'Shift Left' Approach

 Concept:

Moving security checks to the beginning of the project to save money and time.

Simple Explanation:

 Meaning: In a project timeline (from left to right), "Shift Left" means moving security checks to
the start (Left) of the timeline8.
 Why do we do it? (The Cost Factor):
o If you fix a bug during the planning phase, it might cost around $109.
o If you wait and fix that same bug after the software is released, it can cost around $10,00010.
 Key Takeaway: We catch errors early. This saves a huge amount of money and time11.

Topic 4: Traditional SDLC vs. DevSecOps

Concept:

Comparing the old "Waterfall" method with the modern DevSecOps method.

Simple Explanation:

 Traditional (Waterfall) Model:

o The steps happen in a line: Coding -> Building -> Testing -> Security (Last)12.
o Result: This leads to slow software releases and fixes that are very expensive13.
 DevSecOps Model:
o Security is not last. It is part of Coding, Building, Testing, and Deploying14.
o Result: This leads to fast releases and software that is much safer15.

Topic 5: The 5 Phases of DevSecOps

Phase 1: Planning & Threat Modeling

 What happens: Before writing any code, the team tries to guess how hackers might attack the
software16.
 Threat Modeling: This is a brainstorming session to list potential security risks17.
 Example: Planning exactly how to protect user passwords before you even build the login
screen18.

Phase 2: Secure Coding

 Role of Developers: Developers must write code that is clean and secure19.
 Guidelines: They should follow safety rules, such as the OWASP Top 10, which is a list of the
biggest security risks20.
 Tools: Developers use plugins in their coding tools (IDEs) that act like a "spell check," but for
security errors instead of spelling mistakes21.

Phase 3: Building & Testing

 Automation: We use tools (robots) to check the code because they are faster and more accurate
than humans22.
 SAST (Static Testing): This scans the code to find errors while the application is not running23.
 DAST (Dynamic Testing): This tries to "hack" the application while it is running to see if it
breaks24.

Phase 4: Deployment & Release

 Infrastructure as Code (IaC): This means using code to set up servers automatically instead of
doing it manually25.
 Golden Image: This is using a software version that is already approved and secure26.
 Benefit: This prevents human mistakes when setting up servers27.

Phase 5: Monitoring & Response

 Continuous Monitoring: This involves watching the software 24 hours a day, 7 days a week
after it is released28.
 Logging: The system keeps a record (log) of who does what inside the software29.
 Example: If a hacker tries to guess a password 100 times, the system sees this in the logs and
blocks them immediately30.

Topic 6: Key Tools and Benefits

Key Tools in DevSecOps:

You must memorize which tool belongs to which phase31:

 Planning: Jira, Confluence32.

 Coding: Git, VS Code33.
 Scanning: SonarQube, Checkmarx34.
 Container Security: Docker, Kubernetes35.
 Monitoring: Splunk, Nagios36.

4 Major Benefits:

1. Speed: Software is released much faster37.

2. Cost Reduction: Fixing bugs early is much cheaper than fixing them later38.
3. Better Security: Because we test constantly, there are fewer successful hacks39.
4. Compliance: It helps the company follow laws and rules, like GDPR40.
 Topic 7: Conclusion

Summary:

 DevSecOps puts security into every single step of making software41.

 Culture Shift: It changes the team culture so that everyone feels responsible for safety42.
 Final Thought: You cannot have software that is "fast" unless it is also "secure"43.

LECTURE #15
Here are your complete final exam notes based on the lecture slides "Application Security
Threats." These notes are structured to help you answer long questions in your exam.

Topic 1: Introduction to Application Security Threats

Concept:

Understanding what security threats are and how they harm software.

Simple Explanation:

 Definition: These are weaknesses found in software applications1.

 How it works: Attackers exploit (take advantage of) these weaknesses2.
 The Result: This leads to data theft or serious damage to the system3.

Real-Life Example:

A hacked website that leaks private user data to the public4.

Topic 2: Code Injection (Definition & Process)

Concept:

When an attacker forces the application to run bad code.

Simple Explanation:

 What is it? An attacker inserts (injects) malicious code into the application5.
 Why does it happen? The application runs this code without knowing it is bad6. This usually
happens because the application has poor input validation (it doesn't check if the user's input is
safe)7.
 Real-Life Example:

A login form that accepts raw, unchecked input from a user instead of blocking strange
characters8.

Topic 3: Three Main Types of Code Injection

You must know the difference between these three specific examples for the exam:

1. SQL Injection

 Malicious Input Example: The attacker types ' OR '1'='1 into a login box9.
 Result:
o Login Bypass: The system is tricked into letting the attacker in10.
o Database Access: The attacker gets access to the database without needing a real password11.

2. Command Injection

 Malicious Input Example: The user input runs system commands directly on the server12.
 Result:
o The attacker can delete files13.
o Server Takeover: The attacker gains control of the server14.

3. XSS (Script Injection)

 Malicious Input Example: The attacker types a script like

<script>alert('Hacked')</script>15.
 Result:
o Cookie Theft: The attacker steals the user's cookies16.
o Session Hijacking: The attacker takes over the user's active session17.

Topic 4: Impact of Code Injection

Concept:

What happens to the company or user after a Code Injection attack?

Simple Explanation:

 Data Breaches: Sensitive information is leaked18.

 Unauthorized Access: People who should not be there get into the system19.
 System Compromise: The whole system is broken or controlled by the attacker20.
 Real-Life Example:

Customer records are stolen from a company's database21.

Topic 5: Broken Authentication (Definition & Methods)

Concept:

When the system fails to verify who the user actually is.

Simple Explanation:

 What is it? This happens when login mechanisms are weak22.

 The Result: Attackers can bypass the authentication process23. This means the user's identity is
compromised (stolen)24.

Real-Life Example:

A system that uses the same default password for all users, making it easy to guess25.

Topic 6: Three Examples of Broken Authentication

1. Brute Force Attack

 What happens: The attacker tries thousands of different passwords one by one26.
 Result: Account Takeover (the attacker eventually guesses right and takes the account)27.

2. Credential Stuffing

 What happens: The attacker tries using passwords that were leaked or stolen from other
websites28.
 Why it works: Many people use the same password for different sites.

3. Session Hijacking

 What happens: The attacker steals the session ID directly from the user's browser29.
 Result: The attacker can act as the logged-in user without knowing the password30.

Topic 7: Impact of Broken Authentication

Concept:
 The damage caused when login systems fail.

Simple Explanation:

 Identity Theft: Someone else pretends to be you31.

 Financial Fraud: Attackers can steal money32.
 Privacy Loss: Personal information is no longer private33.

Real-Life Example:

An unauthorized money transfer from a bank account34.

Topic 8: Conclusion

Summary:

 Application threats are very common in the real world35.

 Code Injection and Broken Authentication are two of the most dangerous threats36.
 Prevention is necessary to ensure applications remain secure37.

LECTURE # 21(WEEK 11)

Here are your complete final exam notes based on the lecture slides "Security in Cloud-Native
Architectures". These notes are structured to help you answer long questions in your exam.

Topic 1: Cloud-Native Architecture

Concept:

Understanding how modern applications are built to fully utilize the cloud.

Simple Explanation:

 Definition: Cloud-native architecture is an approach where applications are specifically designed

to fully use the features of cloud computing1.
 Focus Areas: It focuses on three main things: scalability (growing easily), flexibility, and fast
deployment using modern technologies2.

Real-Life Example:

Netflix uses cloud-native design to serve millions of users all over the world3.
 Topic 2: Containers

Concept:

Understanding the units that hold applications in a cloud environment.

Simple Explanation:

 Definition: Containers are lightweight units. They package an application together with its
libraries and dependencies4.
 Benefit: They ensure that the application runs consistently (the exact same way) across different
environments5.

Real-Life Example:

A Docker container runs the same app on a laptop and on the cloud without any changes6.

Topic 3: Microservices

Concept:

Breaking an application down into smaller pieces.

Simple Explanation:

 Architecture: Microservices architecture divides a single application into small, independent

services7.
 Function: Each service performs just one single function. These services communicate with
each other via APIs8.

Real-Life Example:

An online store has separate services for different tasks: one for login, one for payment, and one
for orders9.

Topic 4: Importance of Security

Concept:

Why we need to protect cloud-native systems.

 Simple Explanation:

 Goal: Security protects applications, data, and users from cyber threats10.
 Risk Factor: Because cloud systems use multiple components, there are increased chances of an
attack11.

Real-Life Example:

Weak security can lead to the exposure of customer data12.

Topic 5: Container Security (Challenges & Measures)

Concept:

The specific risks associated with using containers and how to fix them.

Challenges:

 Shared OS: Containers share the host Operating System (OS). This increases the risk if the
system is misconfigured13.
 Untrusted Images: If you use images from unknown sources, they may contain vulnerabilities14.
o Example: Using a public image that is infected with malware15.

Measures:

 Scanning & Control: Container security focuses on scanning images for problems and
controlling who has access16.
 Least Privilege: Following the "least privilege principle" reduces the damage from attacks 17.
o Example: Restricting a container's access to the file system18.

Topic 6: Microservices Security (Challenges & Measures)

Concept:

The specific risks associated with breaking apps into microservices and how to protect them.

Challenges:

 Attack Surface: Because there is a large number of services, the "attack surface" (areas that can
be attacked) increases19.
 Communication Risks: The communication between different services can be targeted by
attackers20.
o Example: An attacker intercepts data that is unencrypted21.
 Measures:

 Secure Communication: Use authentication and encryption to secure the communication

between services22.
 Verification: Each service must verify a request before processing it23.
o Example: Using token-based authentication between services24.

Topic 7: Network & Access Security

Concept:

Controlling traffic and permissions within the system.

Simple Explanation:

 Network Security: This controls the internal traffic moving between different services25.
 Access Security: This limits permissions so services only can do what they need to26.

Real-Life Example:

Only the payment service is allowed to access the bank API27.

Topic 8: Monitoring & Incident Response

Concept:

Watching the system for problems and reacting quickly.

Simple Explanation:

 Monitoring: This detects abnormal behavior in the system28.

 Incident Response: This enables the team to take quick action when something goes wrong29.

Real-Life Example:

The system sends an alert after repeated failed login attempts30.

Topic 9: Conclusion

Summary:
 Cloud-native systems need security at every single layer31.
 Both containers and microservices require proper controls32.
 Strong security is the only way to ensure safe cloud applications33.

LECTURE 22 (WEEK 11)

Here are your complete final exam notes based on the lecture slides "Cloud Threats and Attack
Surfaces." These notes are structured to help you answer long questions in your exam.

Topic 1: Introduction to Cloud Threats

Concept:

Understanding the dangers associated with using cloud computing systems.

Simple Explanation:

 Overview: Cloud computing is widely used by many organizations today. However, as cloud
usage grows, security risks also increase1.
 Definition: Cloud threats are possible dangers or risks to cloud systems2.
 What is a Threat? Anything that can harm cloud security is considered a threat3.
 Nature of Threats: They can be intentional (done on purpose) or accidental (done by
mistake)4.
 Targets: These threats can damage data, applications, and cloud services5.

Topic 2: Types of Cloud Threats

Concept:

There are four main types of threats that endanger cloud systems. You must explain each one.

1. Data Breaches

 Explanation: This occurs when unauthorized users get access to data6.

 Consequences: Sensitive information is stolen or leaked7. It affects customer trust and damages
the company's reputation8.
 Cause: It is often caused by weak security or misconfiguration9.
 Example: Customer records are exposed online10.

2. Account Hijacking
 Explanation: Hackers steal login credentials (username and password) to gain control of cloud
accounts11.
 Consequences: Attackers can misuse cloud resources12.
 Cause: This is often caused by using weak passwords13.
 Prevention: Use strong passwords and multi-factor authentication14.

3. Malware Attacks

 Explanation: Malicious software enters the cloud systems15.

 Consequences: This software can damage files or steal data16.

4. Insider Threats

 Explanation: This happens when employees misuse their access to the system17.
 Types: It can be intentional (on purpose) or accidental (by mistake)18.
 Risk: Both malware and insider threats are serious risks to cloud security19.

Topic 3: Cloud Attack Surfaces

Concept:

Understanding where attackers can enter the system and how to close those doors.

Simple Explanation:

 Definition: An attack surface means all the possible entry points where an attacker can enter a
cloud system20.
 Size Matters: Larger systems have larger attack surfaces21. Cloud environments naturally
increase the attack surface because they have more access points, which means more chances for
attacks22.

Examples of Attack Surfaces:

 Login pages and user accounts23.

 APIs and web interfaces24.
 Network connections25.
 Misconfigured cloud storage26.

How to Reduce Attack Surfaces:

 Authentication: Use strong passwords and multi-factor authentication27.

 Configuration: Ensure proper configuration of cloud services28.
 Maintenance: Perform regular updates and apply patches29.
 Oversight: Use continuous monitoring and logging30.
 Goal: A smaller attack surface means better protection31.
 Topic 4: Multi-Cloud Environments

Concept:

Using multiple service providers instead of just one to improve reliability.

Simple Explanation:

 Definition: A multi-cloud environment means using more than one cloud provider at the same
time32.
 Strategy: Organizations do not depend on just a single provider33.

Real-Life Example:

 Using AWS for storage34.

 Using Microsoft Azure for applications35.
 Using Google Cloud for data analytics36.

Why Use Multi-Cloud? (Advantages):

 Independence: Avoids dependence on one cloud provider37.

 Quality: Improves performance and reliability38.
 Safety: Reduces the risk of service failure (if one cloud fails, others still work)39393939.
 Choice: Allows you to choose the best services from different providers40.

Topic 5: Security in Multi-Cloud Environments

Concept:

Managing security becomes harder when using multiple clouds, so specific strategies are needed.

Security Challenges:

 Inconsistency: There are different security rules for each cloud41.

 Visibility: It is difficult to monitor all cloud systems together42.
 Scattered Data: Data is spread across multiple platforms43.
 Complexity: Management becomes more complex and security is more difficult to manage44.

How to Secure Multi-Cloud (Solutions):

 Tools: Use centralized security management tools45.

 Consistency: Apply the same security policies across all clouds46.
 Protection: Use data encryption in every cloud47.
 Checks: Perform regular audits and monitoring48.
 Strategy: Have one unified security strategy for multiple clouds49.

Conclusion

 Cloud threats can seriously affect organizations50.

 To stay safe, attack surfaces must be identified and reduced51.
 While multi-cloud provides benefits, it adds security challenges that require strong planning 52.
 Proper cloud security ensures trust and reliability53.

WEEK #9
Here are the complete final exam notes for Week 9: Incident Response and Forensics. These
notes cover Lectures 17 and 18, structured for easy revision and long-form answer writing.

Lecture 17: Advanced Incident Response Planning & CERT

1. Advanced Incident Response Planning

Concept:

This is a planned method to handle cyber attacks effectively. It is not just about fixing things
after they break, but preparing beforehand. 1

Simple Explanation:

 It is a proactive and systematic approach to managing cybersecurity incidents. 2

 It focuses on four main things: preparing for, detecting, responding to, and recovering from
complex threats. 3
 It combines people, processes, and technology to make the response faster and less damaging. 4

Targets Modern Attacks:

It is designed to handle serious modern attacks such as:

 Advanced Persistent Threats (APTs) 5

 Ransomware and malware outbreaks 6
 Data breaches and insider threats 7

Goal:

It ensures the business can keep running, data is protected, and laws are followed. 8
 2. Objectives of Advanced Incident Response

Concept:

The main goals the organization wants to achieve during an attack.

Key Objectives:

 Minimize Damage: Reduce harm to important information systems and assets. 9

 Early Detection: Find incidents early using continuous monitoring. 10
 Quick Action: Ensure threats are contained (stopped) and eradicated (removed) quickly. 11
 Reduce Losses: Limit financial loss and damage to the company's reputation. 12
 Legal Support: Help meet legal and regulatory requirements. 13
 Improve Resilience: Make the organization stronger against future attacks. 14

3. Key Components of an Incident Response Plan

Concept:

The four stages of handling a security incident.

Step 1: Preparation

 Creating policies, procedures, and "playbooks" (guides) on how to respond. 15

 Providing training and awareness to the response teams. 16

Step 2: Detection and Analysis

 Using security monitoring tools like SIEM (Security Information and Event Management) and
IDS/IPS (Intrusion Detection Systems). 17
 Analyzing logs and using threat intelligence to find problems. 18

Step 3: Containment, Eradication, and Recovery

 Containment: Isolating the affected systems so the infection does not spread. 19
 Eradication: Removing the malicious artifacts (viruses or bad files). 20
 Recovery: Restoring systems and data securely to get back to normal. 21

Step 4: Post-Incident Review

 Looking at lessons learned to improve the plan for next time. 22

 4. Computer Emergency Response Team (CERT)

Concept:

A special team of experts dedicated to handling cyber problems.

Definition:

CERT is a specialized cybersecurity team responsible for handling and responding to cyber
incidents. 23

What CERT Provides:

 Support for incident response. 24

 Threat intelligence and security advisories (warnings). 25
 Analysis of vulnerabilities and advice on how to fix them (mitigation). 26

Types of CERTs:

1. National CERTs: Serve a whole country. 27

2. Organizational CERTs: Serve a specific company or enterprise. 28
3. Industry-specific CERTs: Serve a specific sector (like banking or energy). 29

Note: CERT acts as a trusted authority during major cyber incidents. 30

5. Coordination with CERT

Concept:

Working together with CERT to handle attacks better.

Key Activities:

 Reporting incidents and sharing information about threats. 31

 Doing joint investigations and forensic analysis together. 32
 Getting expert advice on how to contain and recover from the attack. 33

Why Coordinate?

 It helps manage large attacks or attacks that cross borders. 34

 It improves situational awareness (knowing what is happening). 35
 It strengthens the overall cybersecurity posture. 36

6. Benefits and Challenges of Incident Response

 Benefits:

 Speed: Response is faster and more effective. 37

 Less Damage: Reduced downtime and impact on the business. 38
 Compliance: Better security maturity and adherence to laws. 39

Challenges:

 Sharing Limits: It can be hard to share information. 40

 Resources: Lack of skills or resources. 41
 Complexity: Coordinating with others can be complicated. 42

Conclusion for Lecture 17:

Advanced planning is critical. 43Working with CERT improves readiness. 44Continuous

improvement is essential for resilience. 45

Lecture 18: Digital Forensics

1. Digital Forensics: Definition & Objectives

Concept:

The science of finding and analyzing digital evidence for legal or security purposes.

Definition:

Digital Forensics is the process of identifying, collecting, preserving, analyzing, and presenting
digital evidence. 46

Where is it used?

 It investigates cybercrimes, security incidents, and policy violations. 47

 It applies to data from computers, servers, mobile devices, networks, and the cloud. 48

Objectives:

 Identify the source and method of the incident. 49

 Preserve evidence without changing it. 50
 Reconstruct the events that led to the breach. 51
 Support legal cases with credible evidence. 52
 Ensure accountability and stop future crime. 53
 2. The Digital Forensic Process (5 Steps)

Concept:

The standard steps investigators must follow to make sure evidence is valid.

1. Identification:

 Recognizing potential sources where evidence might exist. 54

2. Collection:

 Acquiring (gathering) the data using methods that are sound (reliable). 55

3. Preservation:

 Maintaining the integrity of the data. 56

 Example: Using hashing (digital fingerprints) and secure storage. 57

4. Analysis:

 Examining the data to find relevant information. 58

5. Documentation & Presentation:

 Reporting the findings clearly for both technical people and lawyers. 59

Key Principle:

Evidence must remain unchanged and verifiable throughout the entire process. 60

3. Digital Forensic Techniques

Concept:

Specific methods used to analyze different types of technology.

 Disk and File System Forensics:

o Recovering files that were deleted. 61
o Analyzing file metadata (data about data). 62
 Memory (RAM) Forensics:
o Identifying running processes and malware that lives in memory. 63
 Network Forensics:
o Analyzing traffic and detecting intrusions. 64
 Mobile Device Forensics:
o Analyzing call logs, messages, and app data. 65
 Log and Timeline Analysis:
o Reconstructing events in the order they happened (chronologically). 66

4. Legal Considerations

Concept:

Rules that must be followed so the evidence can be used in court.

 Laws: Must comply with laws governing digital evidence. 67

 Chain of Custody:
o This documents who handled the evidence and when. 68
o It is crucial for proving the evidence was not tampered with.
 Authorization: Proper permission (like warrants or consent) is required. 69
 Admissibility: For evidence to be accepted in court, it depends on:
o Integrity. 70
o Proper handling. 71
o Documentation. 72
 Warning: Failure to follow procedures may invalidate the evidence. 73

5. Ethical Considerations

Concept:

Moral rules for forensic investigators.

 Privacy: Respect privacy and confidentiality. 74

 Access: Only access systems and data you are authorized to see. 75
 Exposure: Avoid exposing personal or sensitive info unnecessarily. 76
 Objectivity: Remain impartial (neutral). 77
 Code of Conduct: Follow professional codes and policies. 78
 Warning: Ethical violations can damage trust and credibility. 79

6. Benefits and Challenges of Digital Forensics

Benefits:

 Allows for accurate investigation of incidents. 80

 Provides reliable evidence for legal support. 81
 Improves security awareness. 82
 Challenges:

 Encryption: Anti-forensic techniques and encryption make analysis hard. 83

 Volume: There is a huge amount of data to search through. 84
 Constraints: Legal and privacy rules limit what can be done. 85

Conclusion for Lecture 18:

Digital forensics is critical for security assurance. 86Success requires proper techniques, legal
compliance, and skilled professionals. 87

WEEK 12(LECTURE 23)

Here are your complete final exam notes based on the lecture slides "Data Privacy by Design:
GDPR, CCPA & Privacy Engineering Model." These notes are structured to help you answer
long questions in your exam.

Topic 1: Privacy by Design

Concept:

Building privacy into the system from the very beginning rather than adding it later.

Simple Explanation:

 Definition: Privacy by Design is a proactive approach. It means privacy and data protection are
built (embedded) into systems, processes, and technologies right from the start1.
 Goal: It ensures user data is protected by default throughout its entire life. It maintains full
functionality, transparency, and user control2.

The 7 Principles of Privacy by Design:

You should memorize these seven core principles:

1. Proactive not Reactive: It prevents privacy issues before they happen, rather than fixing them
after (Preventive not remedial)3.
2. Privacy as the Default Setting: The user does not need to change settings to be safe; privacy is
automatic4.
3. Privacy Embedded into Design: Privacy is a core part of the design, not an add-on5.
4. Full Functionality: This is a "positive-sum" approach, not "zero-sum." It means you can have
both privacy and security without trading one for the other6.
5. End-to-End Security: Data is protected throughout its full lifecycle7.
6. Visibility and Transparency: Operations remain visible and transparent to users and
stakeholders8.
7. Respect for User Privacy: The design must be user-centric (focused on the user's needs)9.

Topic 2: GDPR (General Data Protection Regulation)

Concept:

A strict law that requires privacy to be part of the design process.

Simple Explanation:

 Article 25: This part of the GDPR explicitly requires "Data protection by design and by
default"10.
 Implementation: This means companies must implement technical and organizational safety
measures at two times:
1. When deciding how to process data11.
2. At the time the data is actually processed12.

Core Principles of GDPR:

 Lawfulness, Fairness, Transparency: There must be clear communication with users about
their data13.
 Purpose Limitation: Data should be collected only for specific and explicit purposes14.
 Data Minimization: Collect only the data that is strictly necessary15.
 Storage Limitation: Data must be deleted when it is no longer needed16.

GDPR Data Subject Rights (Individual Rights):

Individuals have specific rights over their data:

 Right of Access: To see their data17.

 Right of Rectification: To correct wrong data18.
 Right to Erasure: Also known as the "Right to be Forgotten" (to delete data)19.
 Right to Restriction of Processing: To limit how data is used20.
 Right of Data Portability: To move data to another service21.
 Right to Object: To say no to processing22.

Topic 3: CCPA (California Consumer Privacy Act)

Concept:

A law focusing on the rights of residents in California to control their personal info.

Simple Explanation:
 Definition: The CCPA gives California residents control over their personal information23.
 Personal Information: This includes any data that identifies or links to a consumer (e.g., names,
IP addresses, purchase history)24.
 Who it applies to: It applies to businesses that meet specific requirements regarding revenue,
the amount of data processed, or revenue earned from selling data25.

Key Difference from GDPR:

 The CCPA focuses heavily on the "Right to Opt-Out" of the sale or sharing of personal
information26.
 Requirement: Businesses must display a clear link on their homepage that says "Do Not
Sell/Share My Personal Information"27.

Key Consumer Rights under CCPA:

 Right to Know: To know what data is being collected28.

 Right to Delete: To delete personal data29.
 Right to Opt-Out: To stop the sale of data30.
 Non-discrimination: Companies cannot treat you badly for using your privacy rights31.

Topic 4: Privacy Engineering Models

Concept:

Using structured tools to identify and fix privacy risks in software.

Purpose:

These models provide methodologies and tools to identify, access, and mitigate privacy risks
throughout the system lifecycle32.

Important Models:

1. LINDDUN Framework:
o A systematic methodology for privacy threat modeling33.
o It is designed to integrate privacy considerations into the early stages of software development 34.
o Acronym meaning: Linkability, Identifiability, Non-repudiation, Detectability, Disclosure of
Information, Unawareness, Non-compliance35.
2. NIST Privacy Framework:
o A voluntary tool to help organizations manage privacy risk36.
o Core Functions: Identify, Govern, Control, Communication, Protect37.
3. PMRM (Privacy Management Reference Model):
o Focuses on data flow and services38.

Tools and Techniques:

 Encryption39.
 Access Control40.
 Anonymization41.

Topic 5: Conclusion & Best Practices

Concept:

How modern teams should handle privacy efficiently.

Best Practices:

 Shift Left: Privacy should start at the "whiteboard" (design phase), not the week before launch42.
 Cross-Functional Collaboration: Legal, Product, and Engineering teams must all speak the
same language and work together43.
 Automation is Key: Manual privacy checks do not work well in fast "Agile" environments, so
automation is necessary44.

WEEK 12(LECTURE 24)

Here are your complete final exam notes based on the lecture slides "Data Anonymization &
Tokenization". These notes are structured to help you answer long questions in your exam.

Topic 1: Data Anonymization

Concept:

Changing data permanently so that nobody can tell who it belongs to.

Simple Explanation:

 Definition: Data anonymization is the process of modifying personal data so that individuals
cannot be identified1.
 How it works: It removes both direct and indirect identifiers from the data2.
 Key Feature: Once the data is anonymized, the original data cannot be recovered3.

Importance:

 It protects personal and sensitive information4.

 It reduces the negative impact if a data breach happens5.
 It supports important privacy laws like GDPR and HIPAA6.
 It allows organizations to safely share data for research and analytics7.
 It minimizes legal and compliance risks for the company8.

Real-World Example (Healthcare):

 Healthcare organizations often need to share patient data for research purposes9.
 To do this safely, they remove names, IDs, and contact details10.
 Only non-identifiable data like age, symptoms, and results are kept11.
 Result: Even if this data is leaked to the public, the identities of the patients remain protected 12.

Topic 2: Tokenization

Concept:

Swapping sensitive data for a random code so the real data stays safe in a vault.

Simple Explanation:

 Definition: Tokenization replaces sensitive data with a random value called a token13.
 The Token: This token has absolutely no meaning outside of the specific system it was created
for14.
 Key Feature: Unlike anonymization, the original data is stored securely elsewhere and can be
retrieved when needed15.

Importance:

 It protects highly sensitive data, such as credit card numbers16.

 It limits exposure to data theft during cyberattacks17.
 It reduces the scope (amount of work) needed for compliance requirements18.
 It is commonly used in payment and banking systems19.
 It improves overall data security20.

Real-World Example (Online Shopping):

 Online shopping websites use tokenization to protect customers21.

 When you pay, your actual credit card number is replaced by a token22.
 The merchants (shops) store only the token, not your card number23.
 Result: Even if hackers steal the data from the merchant, the tokens are useless to them 24.

Topic 3: Advantages & Disadvantages

Data Anonymization:

 Advantages:
o It is best for data sharing and analysis25.
o It offers strong privacy protection26.
 Disadvantage:
o The data cannot be recovered once changed27.

Tokenization:

 Advantages:
o The data can be restored securely when needed28.
o It gives high control over sensitive data29.
 Disadvantage:
o It requires a secure token management system to work30.

Topic 4: Difference between Anonymization and Tokenization

Feature Data Anonymization Tokenization

Original data is stored securely

Recovery No recovery of original data31.
(Reversible)32.

Nature Permanent data protection33. Reversible process34.

Used for analytics and

Primary Use Used in payments and transactions36.
research35.

WEEK 10
Here are your complete final exam notes based on the lecture slides "Security Auditing and
Compliance." These notes are structured to help you answer long questions in your exam.

Topic 1: Security Auditing Overview and the Need for Advanced Methods

Concept:

Security auditing is the "check-up" process for an organization's security health, while advanced
methods are needed to keep up with modern dangers.

Security Auditing Overview:

 Definition: It involves the evaluation of systems, processes, and controls1.

 Purpose: It ensures that data is secure and that the organization follows (complies with)
policies2.
 Goal: It identifies risks and vulnerabilities in the system3.
 Why Do We Need Advanced Auditing?

Traditional methods are no longer enough because:

 Growing Threats: Cyber threats are increasing4.

 Complexity: IT infrastructures are becoming more complex5.
 Manual Limitations: Periodic manual audits (checking once in a while by hand) have
limitations6.
 Speed Requirement: There is a high demand for real-time monitoring7.

Advanced Auditing Methods:

To solve these problems, we use:

 Continuous Auditing8.
 Automated Auditing Tools9.
 Real-time analysis and reporting10.

Topic 2: Continuous Auditing

Concept:

Instead of checking security once a year, Continuous Auditing checks it all the time, non-stop.

What is Continuous Auditing?

 It is an ongoing audit process11.

 It uses real-time or near real-time data analysis12.
 It performs automated control evaluation (machines check the rules, not humans)13.

How It Works (The Process):

1. Continuous Data Collection: The system gathers data constantly14.

2. Control and Rule Evaluation: The system checks this data against set rules15.
3. Automated Alerts: If something is wrong, the system sends automated alerts and reports
immediately16.

Benefits:

 Fraud Detection: It allows for the early detection of fraud17.

 Risk Reduction: It reduces compliance risks18.
 Efficiency: It improves operational efficiency19.
 Decisions: It leads to better decision-making20.

Challenges (Disadvantages):
 Cost: It has a high implementation cost21.
 Integration: Integrating it with existing complex systems is difficult22.
 Skills: It requires skilled professionals to manage23.
 Privacy: It raises data privacy concerns24.

Topic 3: Automated Auditing Tools

Concept:

Using software robots to do the boring and difficult work of auditing faster and better.

What are Automated Auditing Tools?

 These are software tools designed specifically for audit tasks25.

 Key Function: They reduce the manual effort required by humans26.
 Result: They enhance both accuracy and speed27.

The Role of Automation in Audits:

 Continuous Monitoring: Automation allows the system to be watched 24/728.

 Speed: It creates faster audit cycles29.
 Scalability: It is scalable, meaning it works well even for very large organizations30.

Topic 4: Compliance Audits

Concept:

Checking if the company is following the laws and rules.

Overview:

 Definition: An assessment to see if the organization meets legal and regulatory standards31.
 Accountability: It ensures the organization is held accountable for its actions32.
 Prevention: It prevents legal and financial penalties33.

Importance (Why do we do it?):

 Avoid Fines: It stops the company from getting legal fines34.

 Trust: It builds trust with customers and stakeholders35.
 Protection: It protects sensitive data36.
 Reputation: It improves the organization's reputation37.

Topic 5: Key Regulatory Standards (GDPR, PCI DSS, HIPAA, SOX)

 Concept:

You must know these four specific laws and what they focus on for the exam.

1. GDPR (General Data Protection Regulation)

 Overview: An EU regulation focused on privacy and data rights for organizations handling EU
citizens’ data 38.
 Key Audit Areas:
o User consent management39.
o Data protection policies40.
o Breach reporting mechanisms41.

2. PCI DSS (Payment Card Industry Data Security Standard)

 Overview: A security standard for payment card data that applies to merchants and service
providers42.
 Audit Focus:
o Secure network configuration43.
o Encryption of cardholder data44.
o Regular security testing45.

3. HIPAA (Health Insurance Portability and Accountability Act)

 Overview: A US law protecting patient health information (PHI)46.

 Audit Requirements:
o Administrative safeguards47.
o Physical safeguards48.
o Technical safeguards49.
o Risk assessments50.

4. SOX (Sarbanes-Oxley Act)

 Overview: A US law for financial transparency in public companies to prevent financial fraud 51.
 Key Compliance Areas:
o Internal controls52.
o Financial reporting accuracy53.
o IT general controls (ITGC)54.
o Audit trails55.