Cybersecurity CE -1 ANS
Cybersecurity CE -1 ANS
1. SSL
Secure Socket Layer (SSL) provides security to the data that is transferred between web
browser and server. SSL encrypts the link between a web server and a browser which ensures
that all data passed between them remain private and free from attack
Secure Socket Layer Protocols
● SSL Record Protocol
● Handshake Protocol
● Alert Protocol
● Confidentiality
● Message Integrity
In the SSL Record Protocol application data is divided into fragments. The fragment is
compressed and then encrypted MAC (Message Authentication Code) generated by algorithms
like SHA (Secure Hash Protocol) and MD5 (Message Digest) is appended. After that encryption
of the data is done and in last SSL header is appended to the data.
Handshake Protocol
Handshake Protocol is used to establish sessions. This protocol allows the client and server to
authenticate each other by sending a series of messages to each other. Handshake protocol uses
four phases to complete its cycle.
● Phase-1: In Phase-1 both Client and Server send hello-packets to each other. In this IP
session, cipher suite and protocol version are exchanged for security purposes.
● Phase-2: Server sends his certificate and Server-key-exchange. The server end
Client-exchange-key.
● Phase-4: In Phase-4 Change-cipher suite occurs and after this the Handshake Protocol
ends.
SSL Certificate
SSL (Secure Sockets Layer) certificate is a digital certificate used to secure and verify the identity
of a website or an online service. The certificate is issued by a trusted third-party called a
Certificate Authority (CA), who verifies the identity of the website or service before issuing the
certificate.
2. KERBEROS
The Authentication Server performs the initial authentication and ticket for Ticket
Granting Service.
● Database:
The Authentication Server verifies the access rights of users in the database.
The Ticket Granting Server issues the ticket for the Server
Kerberos Overview:
● Step-1:
User login and request services on the host. Thus user requests for ticket-granting
service.
● Step-2:
Authentication Server verifies user’s access right using database and then gives
ticket-granting-ticket and session key. Results are encrypted using the Password of the
user.
● Step-3:
The decryption of the message is done using the password then send the ticket to
Ticket Granting Server. The Ticket contains authenticators like user names and network
addresses.
● Step-4:
Ticket Granting Server decrypts the ticket sent by User and authenticator verifies the
request then creates the ticket for requesting services from the Server.
● Step-5:
● Step-6:
The server verifies the Ticket and authenticators then generate access to the service.
Phishing: Scammers trick you into giving away your personal info, like passwords or credit card numbers, by
pretending to be someone you trust (like a bank or a website).
DDoS Attack: Attackers send so much traffic to a website or server that it crashes, making it unavailable to real users.
SQL Injection: Hackers use a website's search or input boxes to insert harmful commands into its database, letting
them steal or mess with data.
Malware Attacks
Malware refers to malicious software designed to damage or disrupt systems. Common types of malware include:
● Viruses: Malicious programs that attach themselves to legitimate software and spread to other systems.
● Worms: Self-replicating programs that spread across networks without human intervention.
● Trojans: Malware that masquerades as legitimate software to trick users into installing it.
● Ransomware: A type of malware that locks or encrypts files and demands a ransom for their release.
● Spyware: Software that secretly monitors a user’s activities and sends the information to a third party.
● Adware: Software that displays unwanted ads, often bundled with other software.
Masquerade Attack:
In a Masquerade Attack, a hacker pretends to be someone else. They use someone else's identity to gain unauthorized
access to systems or steal information. For example:
● A hacker could send an email pretending to be a trusted person (like your boss) and ask you to do something
harmful, like transferring money or sharing sensitive data.
Modification of Message:
In a Modification of Message attack, a hacker intercepts a message being sent between two parties and changes it
before it reaches the recipient
DMZ receives requests from outside users or public networks to access the information and
website of a company. For such type of request, DMZ arranges sessions on the public network. It
cannot initiate a session on the private network. If anyone tries to perform malicious activity on
DMZ, the web pages are corrupted, but other information remains safe.
The goal of DMZ is to provide access to the untrusted network by ensuring the security of the
private network. DMZ is not mandatory, but a better approach is to use it with a firewall.
The public key infrastructure uses a pair of keys: the public key and the private key to achieve
security.
Encryption:
● If someone wants to send you a secure message, they use your public key to "lock"
(encrypt) the message. Since your private key is the only one that can "unlock"
(decrypt) the message, only you can read it.
Digital Signatures:
● When you send a message, you use your private key to "sign" it. This proves that the
message came from you and hasn’t been tampered with.
● Anyone who gets the message can use your public key to verify your signature,
ensuring that it is really from you and hasn’t been altered.
6. Signature-Based IDS/IPS:
7. Anomaly-Based Method:
Anomaly-based IDS was introduced to detect unknown malware attacks as new malware is
developed rapidly. In anomaly-based IDS there is the use of machine learning to create a trustful
activity model and anything coming is compared with that model and it is declared suspicious if
it is not found in the model. The machine learning-based method has a better-generalized
property in comparison to signature-based IDS as these models can be trained according to the
10 .SET
Secure Electronic Transaction or 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. SET
protocol restricts the revealing of credit card details to merchants thus keeping hackers and
thieves at bay.
● The cardholder enters their credit card details and encrypts them using a secret key.
● They also sign the payment request with their private key to prove it’s really them.
● The merchant sends the encrypted payment info to the payment gateway.
● The payment gateway checks the signature to verify the cardholder’s identity using their digital certificate.
● The bank (issuer) checks the cardholder’s details, like card balance and validity.
● If everything’s good, the bank sends an approval message to the payment gateway.
Example: When checkout from the counter of a market after shopping, the receipt (bill) that we
get is a type of audit trail, we (Who/customer) can find all the necessary information on it like
the date and time (when) of checkout, location of the mall and counter number (Where), and
the items purchased (What/data).