CNS Module 7 — E-mail, Web & System Security | Study Guide

CRYPTOGRAPHY & NETWORK

SECURITY
MODULE 7 — E-mail, Web & System Security
Complete Theory Study Guide · All 11 Topics · Exam-Ready
TOPICS COVERED
• 01 — Email Security
• 02 — S/MIME
• 03 — PGP
• 04 — Web Security Considerations
• 05 — SET Protocol
• 06 — Intruders
• 07 — Intrusion Detection System (IDS)
• 08 — Password Management
• 09 — Firewalls
• 10 — Firewall Design Principles
• 11 — Trusted Systems

TOPIC 01 Electronic Mail Security

DEFINITION
Email Security refers to measures and practices used to protect email communication from
unauthorized access, loss, or attacks. Email is the most widely-used communication medium and
hence a prime target for cyber threats.

KEY THREATS TO EMAIL SECURITY

• Phishing — Fake emails that trick users into revealing sensitive information (passwords, bank
details)
• Spam — Unwanted emails, often containing malicious links or attachments
• Malware — Viruses or ransomware delivered through email attachments or links
• Spoofing — Attackers forge the sender's address to appear trustworthy
• Man-in-the-Middle Attacks — Interception of email communication

THREAT CLASSIFICATIONS (4 CATEGORIES)

• Authenticity-related — Could result in unauthorized access to an enterprise's email system
• Integrity-related — Could result in unauthorized modification of email content
• Confidentiality-related — Could result in unauthorized disclosure of sensitive information
• Availability-related — Could prevent end users from being able to send or receive email

Cryptography & Network Security · All 11 Topics · Exam-Ready

CNS Module 7 — E-mail, Web & System Security | Study Guide

STANDARD PROTOCOLS FOR EMAIL SECURITY

• PGP (Pretty Good Privacy) — Decentralized, user-managed key trust model (Web-of-Trust).
Used primarily for personal use.
• S/MIME (Secure/Multipurpose Internet Mail Extension) — Certificate Authority based trust
model. Recommended by NIST 800-177 for enterprise use.

TOPIC 02 S/MIME — Secure/Multipurpose Internet Mail Extension

WHAT IS S/MIME?
S/MIME is a security enhancement to the MIME Internet email format standard, based on technology
from RSA Data Security. It provides four message-related services: authentication, confidentiality,
compression, and email compatibility.

4 MESSAGE-RELATED SERVICES

Function Typical Algorithm Typical Action

Digital Signature RSA / SHA-256 Hash code of message created using SHA-256; digest
encrypted with sender's private key and included with
message
Message AES-128 with CBC Message encrypted using AES-128/CBC with a one-time
Encryption session key; session key encrypted using RSA with
recipient's public key and included with the message
Compression Unspecified A message may be compressed for storage or
transmission
Email Compatibility Radix-64 Encrypted message converted to ASCII string using
conversion radix-64 conversion for email application transparency

S/MIME FUNCTIONAL FLOW — SENDER SIDE

The sender signs, then encrypts the message:
1. Step 1: Sign message — using RSA/SHA-256 with sender's private key → produces message +
signature (sig)
2. Step 2: Generate one-time session key — for AES-128/CBC encryption
3. Step 3: Encrypt message + sig — using AES-128/CBC with the one-time session key
4. Step 4: Encrypt session key — using recipient's public key (RSA) → Digital Envelope
5. Step 5: Send — Encrypted (msg + sig) + Digital Envelope to receiver

Receiver Side:
6. Step 1: Decrypt Digital Envelope — using own private key (RSA) to recover session key
7. Step 2: Decrypt message + sig — using AES-128/CBC with recovered session key
8. Step 3: Verify signature — using sender's public key (RSA/SHA-256) to authenticate

Cryptography & Network Security · All 11 Topics · Exam-Ready

CNS Module 7 — E-mail, Web & System Security | Study Guide

Key insight: Sender signs FIRST, then encrypts. Receiver decrypts FIRST, then verifies.

S/MIME MESSAGE CONTENT TYPES (RFC 5652)

• Data — Inner MIME-encoded message content; may be encapsulated in SignedData,
EnvelopedData, or CompressedData
• SignedData — Used to apply a digital signature to a message
• EnvelopedData — Encrypted content of any type + encrypted-content encryption keys for one or
more recipients
• CompressedData — Used to apply data compression to a message

ENVELOPEDDATA — PREPARATION STEPS

9. Step 1: Generate pseudorandom session key — for symmetric encryption algorithm (RC2/40
or Triple DES)
10. Step 2: Encrypt session key — for each recipient, encrypt with recipient's public RSA key
11. Step 3: Prepare RecipientInfo block — contains: identifier of recipient's public-key certificate,
identifier of algorithm used to encrypt session key, and the encrypted session key
12. Step 4: Encrypt message content — with the session key

SIGNEDDATA — PREPARATION STEPS

13. Step 1: Select a message digest algorithm — (SHA or MD5)
14. Step 2: Compute the message digest — hash function of the content to be signed
15. Step 3: Encrypt the message digest — with the signer's private key
16. Step 4: Prepare SignerInfo block — contains: signer's public-key certificate, identifier of
message digest algorithm, identifier of algorithm used to encrypt message digest, and the
encrypted message digest

CLEAR SIGNING
Clear signing uses the multipart content type with a signed subtype. The message is sent 'in the
clear' — not transformed — so recipients with MIME capability (but NOT S/MIME capability) can still
read the incoming message.
• First part — Original content (if not 7-bit, encoded as base64 or quoted-printable)
• Second part — Detached signature — a signedData object with empty message content field,
transfer encoded using base64. MIME content type: application/pkcs7-signature

CRYPTOGRAPHIC ALGORITHMS USED IN S/MIME

Function Requirement Level & Algorithm

Create message digest for digital MUST support SHA-256 SHOULD support SHA-1 Receiver
signature SHOULD support MD5 (backward compatibility)

Cryptography & Network Security · All 11 Topics · Exam-Ready

CNS Module 7 — E-mail, Web & System Security | Study Guide

Function Requirement Level & Algorithm

Use message digest to form digital MUST support RSA with SHA-256 SHOULD support: DSA
signature with SHA-256, RSASSA-PSS with SHA-256, RSA with SHA-
1, DSA with SHA-1, RSA with MD5
Encrypt session key for transmission MUST support RSA encryption SHOULD support: RSAES-
OAEP, Diffie-Hellman ephemeral-static mode
Encrypt message with one-time MUST support AES-128 with CBC SHOULD support: AES-
session key 192 CBC, AES-256 CBC, Triple DES CBC

NOTE: MUST = absolute requirement (must include to be in conformance). SHOULD = recommended

but valid reasons may exist to ignore.

S/MIME CERTIFICATE PROCESSING

• Certificate Standard — Uses X.509 Version 3 public-key certificates
• Certification Authorities — Certificates are signed by CAs
• Configuration — S/MIME managers/users must configure each client with a list of trusted keys
and certificate revocation lists

User Agent Role — 3 Key Management Functions

• Key Generation — MUST generate separate Diffie-Hellman and DSS key pairs; SHOULD
generate RSA key pairs. RSA key length: 768–1024 bits (MUST NOT be less than 512 bits).
Keys generated from nondeterministic random input.
• Registration — User's public key must be registered with a CA to receive an X.509 public-key
certificate
• Certificate Storage & Retrieval — User requires access to a local list of certificates to verify
incoming signatures and encrypt outgoing messages

ENHANCED SECURITY SERVICES (RFC 2634) — 4 SERVICES

• Signed Receipts — A signed receipt may be requested in a SignedData object. Provides proof
of delivery to the originator; recipient signs original message + sender's signature to form new
S/MIME message
• Security Labels — Security label included in authenticated attributes of SignedData object.
Contains security info about content sensitivity. Used for access control (secret, confidential,
restricted) or role-based access (e.g., patient's health-care team, medical billing agents)
• Secure Mailing Lists — S/MIME Mail List Agent (MLA) handles per-recipient encryption for
multi-recipient messages. Originator only encrypts to MLA's public key; MLA performs recipient-
specific encryption.
• Signing Certificates — Securely binds a sender's certificate to their signature through a signing
certificate attribute

Cryptography & Network Security · All 11 Topics · Exam-Ready

CNS Module 7 — E-mail, Web & System Security | Study Guide

TOPIC 03 PGP — Pretty Good Privacy

HISTORY & BACKGROUND

• Creator — Phil Zimmerman; first released in 1991
• Availability — Made available free of charge; became popular for personal use
• Initial Protocol — Proprietary with intellectual property restrictions on some encryption
algorithms
• RFC 1991 (1996) — PGP version 5.x defined in IETF RFC 1991 — PGP Message Exchange
Formats
• OpenPGP — Developed as new standard protocol based on PGP version 5.x
• OpenPGP Standards — RFC 4880 (OpenPGP Message Format, November 2007) and RFC
3156 (MIME Security with OpenPGP, August 2001)

S/MIME VS. OPENPGP — 2 SIGNIFICANT DIFFERENCES

Aspect S/MIME OpenPGP

Key Certification Uses X.509 certificates issued by Users generate their own public/private
Certificate Authorities (CAs) or local keys and solicit signatures from
agencies delegated by a CA. Trusted if individuals or organizations they know.
there is a valid PKIX chain to a trusted Trusted if signed by another trusted
root. OpenPGP key. This is called the Web-
of-Trust.
Key Distribution Certificate included with signed Does NOT include sender's public key
messages; managed by CAs. with each message. Recipients must
separately obtain sender's public key.
Keys posted on TLS-protected websites
or registered with OpenPGP public key
servers. No vetting of keys — users rely
on Web-of-Trust.

NIST Recommendation: NIST 800-177 recommends the use of S/MIME rather than PGP because of
the greater confidence in the CA system of verifying public keys.

TOPIC 04 Web Security Considerations

WHY WEB SECURITY IS CHALLENGING

• Complexity — Underlying software is extraordinarily complex, hiding many potential security
flaws
• Attack Gateway — A Web server can be exploited as a launching pad into the corporation's or
agency's entire computer complex. Once subverted, attackers may access data and systems
beyond the Web itself.

Cryptography & Network Security · All 11 Topics · Exam-Ready

CNS Module 7 — E-mail, Web & System Security | Study Guide

• Untrained Users — Casual and untrained (in security matters) users are common clients for
web-based services. Not aware of security risks and do not have tools or knowledge for
countermeasures.

WEB SECURITY THREATS — 4 CATEGORIES (TABLE 17.1)

Category Threats Consequences Countermeasures

Integrity Modification of user data, Loss of information, Cryptographic

Trojan horse browser, Compromise of machine, checksums
Modification of memory, Vulnerability to all other
Modification of message traffic threats
in transit
Confidentiality Eavesdropping on net, Theft of Loss of information, Loss Encryption, Web
info from server, Theft of data of privacy proxies
from client, Info about network
configuration, Info about which
client talks to server

Denial of Killing user threads, Flooding Disruptive, Annoying, Difficult to prevent

Service machine with bogus requests, Prevents user from
Filling up disk or memory, getting work done
Isolating machine by DNS
attacks

Authentication Impersonation of legitimate Misrepresentation of Cryptographic

users, Data forgery user, Belief that false techniques
information is valid

WEB TRAFFIC SECURITY APPROACHES — 3 LEVELS (FIGURE 17.1)

(a) Network Level — IP Security (IPsec)

IPsec is transparent to end users and applications, providing a general-purpose solution. Includes a
filtering capability so only selected traffic incurs the overhead of IPsec processing.

(b) Transport Level — SSL / TLS

Security implemented just above TCP. The foremost example is SSL (Secure Sockets Layer) and its
Internet standard successor TLS (Transport Layer Security). Two implementation choices: (1) part of
underlying protocol suite (transparent to applications), or (2) embedded in specific packages. Virtually
all browsers come equipped with TLS.

(c) Application Level — S/MIME, Kerberos

Application-specific security services embedded within the particular application. Advantage: the
service can be tailored to the specific needs of a given application.

TOPIC 05 SET — Secure Electronic Transaction Protocol

Cryptography & Network Security · All 11 Topics · Exam-Ready

CNS Module 7 — E-mail, Web & System Security | Study Guide

WHAT IS SET?
SET is a security protocol designed to ensure the security and integrity of electronic transactions
conducted using credit cards. Unlike a payment system, SET operates as a security protocol applied to
those payments. It uses different encryption and hashing techniques to secure payments over the
internet done through credit cards.
• Restricts revealing credit card details to merchants — keeping hackers and thieves at bay
• Includes Certification Authorities — for making use of standard Digital Certificates like X.509
Certificate

REQUIREMENTS OF SET (4 KEY REQUIREMENTS)

• Mutual Authentication — Both customer (cardholder) authentication and merchant
authentication must be provided
• Confidentiality — PI (Payment Information) and OI (Order Information) must be kept confidential
by appropriate encryption
• Integrity — Resistive against message modifications — no changes should be allowed in
content being transmitted
• Interoperability — Must be interoperable and make use of the best security mechanisms

PARTICIPANTS IN SET (5)

• Cardholder — The customer
• Issuer — Customer's financial institution (bank)
• Merchant — The seller
• Acquirer — Merchant's financial institution
• Certificate Authority (CA) — Issues standard X.509V3 certificates to all other participants

SET FUNCTIONALITIES

Authentication
• Merchant Authentication — Prevents theft; customers check relationships between merchants
and financial institutions. Standard X.509V3 certificates used for verification
• Customer / Cardholder Authentication — SET checks if credit card is used by an authorized
user using X.509V3 certificates

Message Confidentiality
Prevents unintended people from reading the message. SET implements confidentiality using
encryption techniques. Traditionally DES is used.

Message Integrity
SET does not allow message modification. Messages are protected against unauthorized modification
using RSA digital signatures with SHA-1 and HMAC with SHA-1.

Cryptography & Network Security · All 11 Topics · Exam-Ready

CNS Module 7 — E-mail, Web & System Security | Study Guide

DUAL SIGNATURE — KEY CONCEPT OF SET

The dual signature connects two pieces of information meant for two different receivers:

Information Intended For Purpose

Order Information (OI) Merchant Contains order details

Payment Information (PI) Bank (Acquirer) Contains payment/card details

Sending them in a connected form (rather than separately) resolves any future disputes.

Key Terms:
• PI — Payment Information
• OI — Order Information
• PIMD — Payment Information Message Digest
• OIMD — Order Information Message Digest
• POMD — Payment Order Message Digest
• H — Hashing function
• E — Public key encryption
• KPc — Customer's Private Key
• || — Append (concatenation) operation

Dual Signature: DS = E(KPc, [H(H(PI) || H(OI))])

Steps: Hash(PI) → PIMD | Hash(OI) → OIMD | Concatenate PIMD || OIMD → Hash → POMD |
Encrypt POMD with KPc → Dual Signature

PURCHASE REQUEST GENERATION — 3 INPUTS REQUIRED

• Payment Information (PI)
• Dual Signature
• Order Information Message Digest (OIMD)

Additional components:
• EP — Symmetric key encryption
• Ks — Temporary symmetric key
• KUbank — Public key of bank
• CA — Cardholder / Customer Certificate
Digital Envelope = E(KUbank, Ks)

PURCHASE REQUEST VALIDATION — MERCHANT SIDE

Cryptography & Network Security · All 11 Topics · Exam-Ready

CNS Module 7 — E-mail, Web & System Security | Study Guide

The Merchant verifies by comparing two independently computed POMD values:

• Path 1 — Compute: PIMD || Hash(OI) → Hash → POMD
• Path 2 — Decrypt Dual Signature using KUc (customer's public key) → POMD
If both POMD values match → purchase request is VALID ✓

TOPIC 06 Intruders

DEFINITION
Intruders are unauthorized individuals or entities who want to obtain access to a network or system
to breach its security. Also called hackers. They have immense knowledge and in-depth understanding
of technology and security, and aim to steal confidential information to sell to third parties for personal
or professional gains.

3 TYPES OF INTRUDERS

Type Description Access Level Key Characteristic

(i) NOT authorized to use the OUTSIDER — no Attacks unethically to

Masquerader system; exploits techniques to direct access steal data from outside
gain unauthorized control and
steal data
(ii) Misfeasor IS authorized to use the INSIDER — has Abuses legitimate access
system; misuses granted direct access rights
access and privilege; takes
undue advantage of
permissions given
(iii) Has supervisory/administrative Can be INSIDER or Can bypass audit
Clandestine control; misuses authoritative OUTSIDER controls; supervisory
User power, often for financial gains authority

TOPIC 07 Intrusion Detection System (IDS)

DEFINITION
An IDS observes network traffic for malicious transactions and sends immediate alerts when
observed. It is software that checks a network or system for malicious activities or policy violations.
Each illegal activity or violation is recorded centrally using a SIEM system or notified to an
administrator. Goal: build a predictive classifier to distinguish 'bad connections' (intrusions) from 'good
(normal) connections'.

4 COMMON METHODS OF INTRUSION

• Address Spoofing — Hiding the source of an attack by using fake or unsecured proxy servers,
making it hard to identify the attacker

Cryptography & Network Security · All 11 Topics · Exam-Ready

CNS Module 7 — E-mail, Web & System Security | Study Guide

• Fragmentation — Sending data in small pieces to slip past detection systems

• Pattern Evasion — Changing attack methods to avoid detection by IDS systems that look for
specific patterns (signature-based)
• Coordinated Attack — Using multiple attackers or ports to scan a network, confusing the IDS
and making it hard to identify what is happening

HOW IDS WORKS — 5 STEPS

17. Step 1: Monitor — Monitors traffic on a computer network for suspicious activity
18. Step 2: Analyze — Analyzes data flowing through the network to look for patterns and signs of
abnormal behavior
19. Step 3: Compare — Compares network activity to a set of predefined rules and patterns to
identify potential attacks
20. Step 4: Alert — If a match is found, sends an alert to the system administrator
21. Step 5: Respond — Administrator investigates the alert and takes action to prevent damage or
further intrusion

6 TYPES / CLASSIFICATIONS OF IDS

(i) Network Intrusion Detection System (NIDS)

Set up at a planned point within the network to examine traffic from ALL devices on the network.
Performs observation of passing traffic on the entire subnet and matches traffic to a collection of known
attacks. Once an attack or abnormal behavior is identified, an alert is sent to the administrator.
Example: Installing NIDS on the subnet where firewalls are located to see if someone is trying to crack
the firewall.

(ii) Host Intrusion Detection System (HIDS)

Runs on independent hosts or devices on the network. Monitors incoming and outgoing packets from
that specific device only. Takes a snapshot of existing system files and compares with the previous
snapshot. If files were edited or deleted, an alert is sent.
Example: Used on mission-critical machines not expected to change their layout.

(iii) Hybrid Intrusion Detection System

Made by the combination of two or more approaches to IDS. Host agent/system data is combined with
network information to develop a complete view of the network system. More effective than other IDS
types.
Example: Prelude.

(iv) Application Protocol-Based IDS (APIDS)

Resides within a group of servers. Identifies intrusions by monitoring and interpreting communication on
application-specific protocols.

Cryptography & Network Security · All 11 Topics · Exam-Ready

CNS Module 7 — E-mail, Web & System Security | Study Guide

Example: Monitoring the SQL protocol explicitly to middleware as it transacts with the database in the
web server.

(v) Protocol-Based IDS (PIDS)

Resides at the front end of a server, controlling and interpreting the protocol between a user/device and
the server. Monitors the HTTPS protocol stream and accepts the related HTTP protocol. Sits in the
interface between server and clients.

(vi) Signature-Based Detection

Checks network packets for known patterns linked to specific threats. Compares packets to a database
of attack signatures and raises an alert if a match is found. Requires regular updates to detect new
threats.
Limitation: Unknown attacks without signatures can bypass this system entirely.

TOPIC 08 Password Management

DEFINITION
Password management refers to methods used to create, store, protect, and manage passwords
so that only authorized users can access systems and data. Weak or reused passwords are one of the
main ways attackers gain access to a network. Compromised credentials remain a major cause of
security breaches.
Modern fact: Modern attacks often succeed simply because users choose easy passwords such as
'123456' or reuse the same password everywhere.

6 KEY PRINCIPLES OF PASSWORD MANAGEMENT

(i) Use Strong Passwords

Passwords should be long and difficult to guess. Long passphrases are safer and easier to remember.
Security experts recommend at least 12–16 characters. Length is more important than many special
symbols.

Type Example

Weak admin123
Strong BlueRiver!CoffeeTrain2026

(ii) Use a Different Password for Every Account

If one account is hacked and the same password is reused elsewhere, attackers can enter multiple
systems. Unique passwords prevent this chain reaction.

(iii) Use a Password Manager

Cryptography & Network Security · All 11 Topics · Exam-Ready
CNS Module 7 — E-mail, Web & System Security | Study Guide

Software that securely stores all passwords in an encrypted vault. The user only needs to remember
one master password.
• Examples — Bitwarden, 1Password, NordPass
• Capabilities — Generate strong passwords, store passwords securely, autofill login details,
reduce password reuse
Considered essential because most people have too many accounts to remember securely.

(iv) Enable Multi-Factor Authentication (MFA)

MFA adds another layer of security, such as a code sent to a phone or an authenticator app. Even if a
password is stolen, the attacker still cannot log in easily. MFA is considered one of the most
important security controls.

(v) Avoid Unsafe Storage Methods

Never store passwords on:
• Sticky notes
• Plain text files
• Unprotected spreadsheets
• Browser notes without encryption
Use encrypted password managers instead.

(vi) Change Passwords Only When Necessary

Modern guidance: change passwords only if: they are leaked, the account is hacked, or suspicious
activity is noticed. Frequent forced changes often lead to weaker passwords.

ORGANIZATIONAL PASSWORD POLICIES

• Minimum password length requirement
• Password history checks (prevent reuse)
• Account lockout after repeated failed attempts
• Mandatory MFA
• Role-based access control (RBAC)

TOPIC 09 Firewalls

DEFINITION
A firewall is a network security system (hardware or software) that monitors and controls incoming
and outgoing traffic based on predefined rules. It acts as a security guard, filtering data packets.

Cryptography & Network Security · All 11 Topics · Exam-Ready

CNS Module 7 — E-mail, Web & System Security | Study Guide

Action Meaning
Accept Allow the traffic through
Reject Block with an error response sent back to the sender

Drop Block silently without any response

IMPORTANCE OF FIREWALLS — 5 REASONS

• Prevent Unauthorized Access — Like a locked door with a guard — only trusted users and
traffic are allowed through
• Block Malicious Traffic — Harmful data such as viruses, phishing attempts, or DoS attacks are
stopped before reaching the system
• Protect Sensitive Information — Safeguards personal and business data from theft or
accidental leaks
• Control Network Usage — Enforces policies such as parental controls, workplace restrictions,
or government filtering
• Mitigate Insider Risks — Detects suspicious applications or data exfiltration attempts from
within the network

HOW A FIREWALL WORKS — 6 STEPS

22. Step 1: All traffic must pass through the firewall — every data packet entering or leaving the
network must first pass through it
23. Step 2: Examine each packet — the firewall examines each packet against predefined security
rules set by the organization
24. Step 3: Allow or block — if packet matches safe rules → allowed; if suspicious, blacklisted, or
contains malicious content → blocked
25. Step 4: Log and alert — blocked or unusual traffic is recorded in logs; real-time alerts
generated for serious threats
26. Step 5: Apply default policy — since not every rule can be predefined, the firewall applies a
default policy (accept, reject, or drop)
27. Step 6: Best practice — setting the default policy to DROP or REJECT is considered best
practice to prevent unauthorized access

TOPIC 10 Firewall Design Principles

5 FIREWALL DESIGN PRINCIPLES

1. Developing Security Policy

Security policy is the most essential part of firewall design. It is designed according to the requirements
of the company or client to determine which kind of traffic is allowed to pass. Without a proper security
policy, it is impossible to restrict or allow specific users. A properly developed security policy also

Cryptography & Network Security · All 11 Topics · Exam-Ready

CNS Module 7 — E-mail, Web & System Security | Study Guide

defines what to do in case of a security breach. Without it, there is an increase in risk as there will not
be a proper implementation of security solutions.

2. Simple Solution Design

If the design of the solution is complex, it will be difficult to implement. A simple design is easier to
implement and maintain. It can be upgraded according to new possible threats while leaving an efficient
but simple structure. The problem with complex designs is configuration errors that open a path for
external attacks.

3. Choosing the Right Device

Every network security device has its purpose and way of implementation. Using the wrong device for
the wrong problem makes the network vulnerable. Using an outdated device for designing a firewall
exposes the network to risk and is almost useless. The design must be done first, then product
requirements must be identified — fitting a product into an existing design weakens security.

4. Layered Defense
Network defense must be multiple-layered in the modern world. If security at one layer is broken, the
network will be exposed to external attacks. Multilayer security design deals with different levels of
threat and gives an edge to the security design, neutralizing attacks more effectively.

5. Consider Internal Threats

While giving a lot of attention to safeguarding the network from external attacks, security often becomes
weak against internal attacks — and most attacks are done internally as it is easy to access and
designed weakly. Different levels can be set in network security while designing internal security.
Filtering can be added to track traffic moving from lower-level security to higher-level security.

TOPIC 11 Trusted Systems

DEFINITION & OVERVIEW

Trusted Systems are special systems designed to serve the purpose of providing security. They
protect against malicious software and third-party intruders, allow only verified users to access the
computer system, and provide security at different levels based on different parameters.

3 TYPES OF TRUSTED SYSTEMS

(i) Multilevel Security

Ensures security is maintained at different levels of the computer system. Prevents information from
being at risk.

Cryptography & Network Security · All 11 Topics · Exam-Ready

CNS Module 7 — E-mail, Web & System Security | Study Guide

Security Level Priority

Top Secret Highest Priority
Secret Second Priority

Confidential Third Priority

Unclassified Lowest Priority

• Flow of information is restricted if security is not cleared at one particular level

CRITICAL RULE: 'Read Up' and 'Write Down' operations are NOT permitted in multilevel security.

(ii) Data Access Control

Provides additional security to the verified process of log-in. Helps in setting permissions for different
users, giving them limited access and restricting any additional accesses. Three basic models:

Model Components Structure

Access Matrix Subject + Object + Access Right Combined view of all

access rights

Access Control List Entries of objects depicting user access and level Column-wise split —
(ACL) of access granted (public or private) object-oriented view
Capability List Authorized users and the granted operations for Row-wise split — subject-
them; users can have multiple capability tickets oriented view

(iii) Reference Monitor

Provides hardware-level security by limiting the access to objects. Maintains security rules ensuring
that 'Read Up' and 'Write Down' operations are NOT performed. Ensures the entire security maintaining
process is verified and safe.

IMPORTANCE OF TRUSTED SYSTEMS — 5 POINTS

• Identity Verification — Ensures only verified users are given access; each user is identified
uniquely
• Safety Maintained — Prevents direct access to confidential information
• Limiting Access — Only absolutely necessary permissions and access granted; unwanted rules
and permissions avoided
• Preventing Malicious Activities — Mechanism in place to detect and prevent hacking attempts
and unauthorized access
• Ensuring Compliance — Helps organizations comply with regulations and standards such as
HIPAA, PCI-DSS, and SOX by providing a secure environment for sensitive information

Cryptography & Network Security · All 11 Topics · Exam-Ready

CNS Module 7 — E-mail, Web & System Security | Study Guide

QUICK REVISION — EXAM CHEAT SHEET

Key facts to memorise for full marks

Topic / Concept Must-Know Fact

S/MIME Services (4) Authentication, Confidentiality, Compression, Email

Compatibility

S/MIME Digital Signature Algorithm RSA / SHA-256

S/MIME Message Encryption (MUST) AES-128 with CBC
S/MIME Message Encryption AES-192 CBC, AES-256 CBC, Triple DES CBC
(SHOULD)
S/MIME Email Compatibility Radix-64 conversion
S/MIME Content Types (4) Data, SignedData, EnvelopedData, CompressedData
S/MIME Certificate Standard X.509 Version 3

S/MIME Enhanced Services (RFC Signed Receipts, Security Labels, Secure Mailing Lists,
2634) Signing Certificates
S/MIME RSA Key Length 768–1024 bits (MUST NOT be less than 512 bits)
PGP Created by / Year Phil Zimmerman / 1991
PGP Trust Model Web-of-Trust

OpenPGP Standards RFC 4880 (format) and RFC 3156 (MIME security)
NIST Recommendation S/MIME preferred over PGP — greater CA confidence
Web Threat: Integrity Cryptographic checksums
Countermeasure

Web Threat: Confidentiality Encryption, Web proxies

Countermeasure
Web Threat: DoS Countermeasure Difficult to prevent
Web Threat: Authentication Cryptographic techniques
Countermeasure
SET — NOT a payment system It is a SECURITY PROTOCOL applied to payments

SET Encryption for Confidentiality DES (traditional)

SET Integrity Mechanism RSA digital signatures with SHA-1 and HMAC with SHA-1
SET Dual Signature Formula DS = E(KPc, [H(H(PI) || H(OI))])

SET Participants (5) Cardholder, Issuer, Merchant, Acquirer, Certificate Authority

Purchase Request Inputs (3) PI, Dual Signature, OIMD
Digital Envelope Formula E(KUbank, Ks)
Intruder Types (3) Masquerader (outsider), Misfeasor (insider), Clandestine User
(either)
IDS Types (6) NIDS, HIDS, Hybrid, APIDS, PIDS, Signature-Based

Cryptography & Network Security · All 11 Topics · Exam-Ready

CNS Module 7 — E-mail, Web & System Security | Study Guide

Topic / Concept Must-Know Fact

Hybrid IDS Example Prelude
Signature-Based IDS Limitation Cannot detect unknown attacks without signatures

IDS Intrusion Methods (4) Address Spoofing, Fragmentation, Pattern Evasion,

Coordinated Attack
Password Minimum Length 12–16 characters
Password Manager Examples Bitwarden, 1Password, NordPass

Firewall Default Policy (Best Practice) Drop or Reject (NOT Accept)

Firewall Actions (3) Accept, Reject, Drop
Firewall Design Principles (5) Security Policy, Simple Design, Right Device, Layered
Defense, Consider Internal Threats
Multilevel Security Levels (High to Top Secret > Secret > Confidential > Unclassified
Low)

Multilevel Security CRITICAL Rule 'Read Up' and 'Write Down' are NOT permitted
Data Access Control Models (3) Access Matrix, Access Control List (column-wise), Capability
List (row-wise)
Reference Monitor Security Level Hardware-level security

Trusted System Compliance HIPAA, PCI-DSS, SOX

Standards
Email Threat Categories (4) Authenticity, Integrity, Confidentiality, Availability

Cryptography & Network Security · All 11 Topics · Exam-Ready