Unit 1 SARA
Unit 1 SARA
✅ Definition
Information Security (INFOSEC) is the practice of protecting information and
information systems from unauthorized access, use, disclosure, disruption, modification, or
destruction.
It ensures that data remains confidential, accurate, and available to authorized users, and
prevents harm to individuals, organizations, or nations due to information compromise.
Objective Description
Confidentiality Ensures that sensitive information is accessed only by authorized users.
Integrity Ensures that information is not altered or tampered with.
Ensures that information and resources are accessible to authorized users
Availability
when needed.
1. Creation
2. Storage (Data at Rest)
3. Processing (Data in Use)
4. Transmission (Data in Transit)
5. Archiving
6. Destruction
Each stage is protected with specific security mechanisms such as encryption, access
control, and secure disposal.
⚙️ Types of INFOSEC
Type Description
Protects network infrastructure (routers, switches, etc.) from attacks
Network Security
like DoS.
Application Secures software apps from bugs, vulnerabilities, and unauthorized
Security use.
Endpoint Security Protects end-user devices like laptops and smartphones.
Data Security Secures data through encryption, masking, or access restrictions.
Cloud Security Secures cloud-based infrastructure, platforms, and applications.
Physical Security Protects hardware, buildings, and facilities where data is stored.
🧠 Summary
• INFOSEC is crucial for protecting digital assets.
• It relies on principles like CIA Triad, authentication, and accountability.
• Threats can be internal or external, intentional or accidental.
• It covers data, networks, applications, devices, and users.
Characteristic Description
Preventing sensitive information from being disclosed to unauthorized
Confidentiality
entities.
Ensuring that data is accurate and unaltered unless by authorized
Integrity
means.
Availability Ensuring that systems and data are accessible to users when required.
Authenticity Verifying that users, data, or systems are genuine.
Preventing denial of an action. For example, ensuring a sender cannot
Non-repudiation
deny having sent a message.
Accountability Tracking who did what and when, through logs and auditing.
Reliability Assuring that systems perform consistently under expected conditions.
Possession/Control Physical control or ownership of information.
🛡️ 3. Availability
➤ Definition:
Availability ensures that data and resources are accessible to authorized users when needed.
➤ Key Aspects:
➤ Countermeasures:
📊 4. Information States
Information typically exists in three distinct states:
⚙️ 5. Processing Security
➤ Definition:
Processing Security refers to protecting data while it's being used or processed in a system
— often the most difficult phase to secure.
➤ Challenges:
➤ Examples of Threats:
• Keyloggers
• Malware
• Insider threats
• RAM scraping attacks
➤ Protection Techniques:
🧠 Summary Table
Concept Key Point
INFOSEC Protects data’s confidentiality, integrity, and availability.
Critical Info
Includes authenticity, non-repudiation, accountability, etc.
Characteristics
Availability Ensures data/systems are accessible when needed.
Data at rest, in transit, in use — each has distinct threats and
Information States
protections.
Processing Security Protects data while it’s actively being used; vulnerable phase.
Part 2
🎓 Countermeasure: Education (Security Awareness & Training)
Example: An employee clicking on a phishing email could lead to malware infection, even if
firewalls and antivirus are in place.
🔒 Conclusion
Education is one of the most cost-effective and impactful countermeasures in Information
Security. It strengthens the "human firewall" — employees — by making them the first line
of defense instead of the weakest link.
Training and Awareness refer to the educational efforts made by organizations to ensure
that employees understand:
They are non-technical countermeasures designed to address the human aspect of security.
Aspect Details
Goal Build general understanding of threats and good security practices.
Audience All employees (technical and non-technical).
Example Activities Posters, email campaigns, newsletters, simulated phishing emails.
Topics Covered Phishing, password safety, social engineering, secure browsing.
Awareness programs are broad and aim to change user behavior through frequent
reminders and simple guidance.
Benefit Explanation
Educated employees are less likely to fall for scams or
Reduces Human Error
mishandle data.
Enhances Incident
Staff can recognize and report threats early.
Response
Promotes Policy
Ensures employees follow company security rules.
Compliance
Fosters an organization-wide attitude of vigilance and
Builds Security Culture
responsibility.
🔐 2. Critical Information
🔹 Definition
Type Examples
Personal Data Names, addresses, social security numbers, biometrics.
Financial Data Credit card details, bank records, transactions.
Health Information Medical histories, prescriptions, diagnoses.
Corporate Secrets Business strategies, R&D data, source code.
Type Examples
Security Credentials Passwords, encryption keys, access tokens.
Government/Military Data Defense plans, intelligence reports.
Control Method
Access Controls Limit data access based on roles.
Encryption Protect data in transit and at rest.
Data Classification Tag data as public, internal, confidential, top secret.
Backup & Recovery Ensure copies exist in case of failure or attack.
Monitoring & Auditing Track who accesses or changes data.
🧠 Summary Table
Concept Key Points
Training and Educate employees to reduce security risks and build a security-first
Awareness culture.
Training In-depth, role-specific skills (e.g., incident handling, secure coding).
Awareness General understanding for all users (e.g., avoid phishing).
Critical Data whose compromise could lead to significant loss or damage.
Information Must be identified and protected.
✅ 1. Confidentiality
🔹 Definition:
Confidentiality means ensuring that information is only accessible to authorized users and
is not disclosed to unauthorized individuals, systems, or processes.
🔹 Why It Matters:
• Privacy violations
• Identity theft
• Legal penalties
• Reputational damage
Control Description
Access Control Assign permissions based on roles (Role-Based Access Control - RBAC).
Encryption Encrypt data at rest and in transit.
Authentication Strong methods like multi-factor authentication (MFA).
Data Masking Hide sensitive parts of data from unauthorized users.
Security Policies Define who can access what and under what conditions.
🔹 Example:
Only HR personnel should access employee salary details. If a regular employee accesses
them, it’s a breach of confidentiality.
✅ 2. Integrity
🔹 Definition:
Integrity ensures that data remains accurate, consistent, and unaltered, except by
authorized means. It protects data from unauthorized modification, deletion, or corruption.
🔹 Why It Matters:
• Financial transactions
• Legal documents
• Health records
must not be changed maliciously or accidentally.
🔹 Threats to Integrity:
Threat Example
Malware Ransomware that modifies or encrypts files.
Insider Attacks Employees modifying logs or records.
Transmission Errors Data corruption during network transit.
Method Description
Hashing Verify data has not been altered (e.g., using SHA-256).
Checksums/CRCs Detect errors in data transmission.
Digital Signatures Authenticate source and ensure message hasn't changed.
Audit Logs Record all changes for traceability.
Version Control Track changes in data or source code.
🔹 Example:
If a bank transaction log is tampered with to remove ₹10,000 from a customer’s record,
integrity has been violated.
🧠 Conclusion
In Information Security, protecting critical information means preserving multiple
characteristics, especially:
These form the foundation of trust and control in any secure information system.
Each state has different security requirements and risks, and must be protected using
suitable security controls.
Data at rest refers to information that is stored on a device or medium and is not actively
moving through the network or being processed.
🔹 Examples:
Threat Description
Theft Physical or digital theft of storage devices.
Unauthorized Access Hackers or insiders accessing stored files.
Data Breaches Exposure of sensitive files stored without proper controls.
🔹 Security Measures:
Method Description
Encrypt stored data using AES, RSA, etc., to prevent unauthorized
Encryption
reading.
Access Control Use role-based access or file permissions to limit data access.
Physical Security Lock servers, use surveillance, restrict physical access.
Backup &
Ensure data is regularly backed up and recoverable.
Redundancy
Data Classification Identify and prioritize protection of sensitive stored data.
Example: A hospital encrypts medical records stored on its database server to ensure that
even if the server is stolen, the data remains secure.
Data in transit refers to information actively moving from one location to another, such as
across the internet or a private network.
🔹 Examples:
• Sending emails
• Uploading/downloading files
• API communications between services
• VoIP calls
🔹 Key Threats:
Threat Description
Intercepting data during transmission (e.g., via packet
Eavesdropping
sniffers).
Threat Description
Man-in-the-Middle (MITM)
Attacker intercepts and possibly alters data mid-transit.
Attacks
🔹 Security Measures:
Method Description
Encryption Use TLS/SSL for secure web traffic (HTTPS), VPNs, IPsec.
Authentication Confirm identity before allowing data exchange.
Integrity Checks Use digital signatures or checksums to detect tampering.
Data in use refers to information that is currently being accessed, processed, or updated
by a system or user.
🔹 Examples:
🔹 Key Threats:
Threat Description
Memory Scraping Attacks that read data from RAM during processing.
Unauthorized Applications Malware gaining access to sensitive processes.
Privilege Escalation Users or processes gaining unauthorized access.
🔹 Security Measures:
Method Description
Endpoint Security Use antivirus, anti-malware, and secure OS configurations.
Access Control Ensure only authorized processes can use the data.
Sandboxing Isolate programs to reduce the impact of malware.
🧠 Final Note:
Each state of information requires custom security mechanisms:
Together, these help enforce Confidentiality, Integrity, and Availability (CIA) across the
entire information lifecycle.
Transmission refers to the movement of data from one location to another — across
networks, between devices, or over the internet.
🔹 Examples:
• Sending an email
• Uploading files to cloud storage
• Transmitting data between servers or APIs
• Online banking transactions
Threat Description
Eavesdropping Attackers intercept data (e.g., via packet sniffers).
Man-in-the-Middle (MITM) Intercept and alter communications.
Data Tampering Modify data during transfer.
Replay Attacks Re-sending previously captured data packets.
🔹 Goals of Transmission Security:
🔒 Example: HTTPS uses SSL/TLS encryption to secure your data during online banking.
📜 3. Countermeasure: Policy
🔹 Definition:
A security policy is a formal set of rules and guidelines that govern how an organization
protects its data, systems, and resources.
Benefit Description
Consistency Everyone follows the same rules and practices.
Accountability Users are aware of responsibilities and consequences.
Compliance Helps meet legal, regulatory, and audit requirements.
Risk Reduction Minimizes likelihood of human error and misbehavior.
✅ Summary Table
Concept Description
Data in motion between devices/networks. Vulnerable to interception
Transmission
and tampering.
Transmission
Use encryption, VPNs, digital signatures to protect data in transit.
Security
Written rules to control user/system behavior and reduce risk. A vital
Security Policy
non-technical countermeasure.
Procedures and practices are the step-by-step methods and daily activities followed by an
organization to enforce its security policies and safeguard information assets.
They serve as operational tools that translate security policies into actionable behavior.
🔸 Security Procedures
These are documented, detailed instructions that describe exactly how to perform a
specific task securely.
Examples:
🔸 Security Practices
These are the recommended ways of working (best practices) that help maintain security
across an organization.
Examples:
🔹 Benefits
Benefit Explanation
Consistency Everyone handles security the same way.
Accountability Tracks who did what and when.
Prevention Reduces chances of human error and misconfigurations.
Compliance Supports audits and meets regulatory requirements.
⚠️ 2. Threats
🔹 Definition
A threat is any potential danger that can exploit a vulnerability to cause harm to
information systems, data, or operations.
🔹 Types of Threats
Type Examples
Natural Earthquakes, floods, fires
Human Hackers, insider threats, social engineers
Technical Malware, phishing, DDoS attacks
Environmental Power failure, hardware breakdown, overheating
• Hackers/crackers
• Malicious insiders
• Nation-states
• Criminal organizations
• Untrained users (accidental threats)
🔹 Impact of Threats
• Data breach
• Service disruption
• Financial loss
• Legal action
• Reputational damage
🔓 3. Vulnerabilities
🔹 Definition
🔹 Types of Vulnerabilities
Type Examples
Software Unpatched software, buffer overflows
Type Examples
Hardware Insecure ports, outdated firmware
Human Poor password habits, lack of training
Organizational Weak policies, lack of backups
Physical Unlocked server rooms, no CCTV
🔹 Common Examples
Vulnerability Threat
Weak passwords Brute-force attacks
Unpatched OS Malware infection
Unencrypted data Data theft during transmission
Open ports Network intrusion
🧠 Summary Table
Concept Definition Example
Procedures Step-by-step tasks to enforce security Resetting a password securely
Practices Everyday habits that reduce risk Using strong passwords
Threats Potential causes of harm Phishing, ransomware
Vulnerabilities Weaknesses that threats exploit Outdated antivirus software
🛡️ Example Scenario
A hacker (threat) finds an unpatched server (vulnerability) and installs ransomware. If the
organization had followed a procedure to apply patches weekly and a practice of monitoring
logs, the attack could have been prevented or mitigated.