Mca 302
Mca 302
ROLL NO : 201DDE1184
COURSE : MCA
YEAR/SEM : 2nd / 3rd
PAPER CODE : MCA 302
PAPER NAME : (NETWORK SECURITY & ADMINISTRATION)
Q-1. Why do we need communication protocol?
Communicating systems use well-defined formats for exchanging various messages. Each
message has an exact meaning intended to elicit a response from a range of possible
responses pre-determined for that particular situation. The specified behavior is typically
independent of how it is to be implemented. Communication protocols have to be agreed
upon by the parties involved. To reach an agreement, a protocol may be developed into a
technical standard. A programming language describes the same for computations, so there
is a close analogy between protocols and programming languages: protocols are to
communication what programming languages are to computations. An alternate
formulation states that protocols are to communication what algorithms are to
computation.
Internet communication protocols are published by the Internet Engineering Task Force
(IETF). The IEEE handles wired and wireless networking and the International Organization
for Standardization (ISO) handles other types. The ITU-T handles telecommunication
protocols and formats for the public switched telephone network (PSTN). As the PSTN and
Internet converge, the standards are also being driven towards convergence
Ans:- Non-repudiation is the assurance that someone cannot deny the validity of something.
Non-repudiation is a legal concept that is widely used in information security and refers to a
service, which provides proof of the origin of data and the integrity of the data. In other
words, non-repudiation makes it very difficult to successfully deny who/where a message
came from as well as the authenticity and integrity of that message.
Digital signatures (combined with other measures) can offer non-repudiation when it comes
to online transactions, where it is crucial to ensure that a party to a contract or a
communication can't deny the authenticity of their signature on a document or sending the
communication in the first place. In this context, non-repudiation refers to the ability to
ensure that a party to a contract or a communication must accept the authenticity of their
signature on a document or the sending of a message.
From the point of view of information security, non-repudiation usually applies to cases of a
formal contract, a communication, or the transfer of data. Its aim is to ensure that an
individual or organization bound by the terms of a contract, or the parties involved in a
particular communication or document transfer are unable to deny the authenticity of their
signatures on the contract documents, or that they were the originator of a particular
message or transfer.
Digital signatures are not sufficient for non-repudiation -- not by a long shot.
I'm afraid much of the cryptographic research community has screwed this up. Researchers
have written many technical papers that claim to address "the non-repudiation problem",
trying to solve it with mathematics -- but what they've failed to accept is that there is a
tremendous gap between the crypto-mathematics and the pragmatics and legal issues. And
unfortunately, the hardest part of the problem to solve is not the mathematics, but rather
the pragmatics and legal issues. Unfortunately, this seems to be a long-standing blind spot
within the cryptographic research community.
Here are some of the challenges to achieving true non-repudiation that a court or lawyer
would be satisfied with:
Malware. What if Grandpa's computer is infected with malware, which steals his private
key? Are we going to hold him responsible for anything signed by that malware -- even if it
means he loses his house? That'd be ridiculous. In particular, an easy way to repudiate is
simply to claim "my private key must have been leaked/stolen".
Similar remarks can be made about social engineering. When social engineering attacks
have a good chance of being successful at stealing the private key, and when the scheme is
designed in such a way that ordinary people cannot use it securely, and when the designers
know (or should have known) this, I think it is questionable whether jurors will be willing to
hold Grandpa responsible, simply because he got screwed by a poorly-designed security
system.
Humans vs. computers. Legally, non-repudiation is about the actions of a human. A court
is going to be looking for evidence that a human (e.g., Grandpa) assented to the terms of
the contract/transaction. The cryptographic schemes cannot achieve that. They can only
show that some computer performed some action. Cryptographers like to assume that the
computer acts as an agent of the human and the computer's actions can stand in for the
human's actions, but this is not a reasonable assumption. For example, malware on the
person's computer can apply the private key without the human's consent.
Q-3. Give a detailed account of why the three-way handshake is a security threat.
Ans:- 3-Way Handshake Process
This could also be seen as a way of how TCP connection is established. Before getting into
the details, let us look at some basics. TCP stands for Transmission Control Protocol which
indicates that it does something to control the transmission of the data in a reliable way.
The process of communication between devices over the internet happens according to the
current TCP/IP suite model(stripped out version of OSI reference model). The Application
layer is a top pile of stack of TCP/IP model from where network referenced application like
web browser on the client side establish connection with the server. From the application
layer,the information is transferred to the transport layer where our topic comes into
picture. The two important protocols of this layer are – TCP, UDP(User Datagram Protocol)
out of which TCP is prevalent(since it provides reliability for the connection established).
However you can find application of UDP in querying the DNS server to get the binary
equivalent of the Domain Name used for the website.
The steps 1, 2 establish the connection parameter (sequence number) for one direction and
it is acknowledged. The steps 2, 3 establish the connection parameter (sequence number)
for the other direction and it is acknowledged. With these, a full-duplex communication is
established.
Cryptography techniques
1. Confidentiality:
Information can only be accessed by the person for whom it is intended and no
other person except him can access it.
2. Integrity:
Information cannot be modified in storage or transition between sender and
intended receiver without any addition to information being detected.
3. Non-repudiation:
The creator/sender of information cannot deny his or her intention to send
information at later stage.
4. Authentication:
The identities of sender and receiver are confirmed. As well as destination/origin of
information is confirmed.
Symmetric-key cryptography
Symmetric-key cryptography, where a single key is used for encryption and decryption
Symmetric-key cryptography refers to encryption methods in which both the sender and
receiver share the same key (or, less commonly, in which their keys are different, but
related in an easily computable way). This was the only kind of encryption publicly known
until June 1976.
Public-Key Cryptography: This is the most revolutionary concept in the last 300-400 years.
In Public-Key Cryptography two related keys (public and private key) are used. Public key
may be freely distributed, while its paired private key, remains a secret. The public key is
used for encryption and for decryption private key is used.
Hash Functions: No key is used in this algorithm. A fixed-length hash value is computed as
per the plain text that makes it impossible for the contents of the plain text to be recovered.
Hash functions are also used by many operating systems to encrypt passwords.
Q-5. 1. Define the following terms: (i) Hacker (ii) Hacktivist (iii) Cracker
Hacker:-
A computer hacker is any skilled computer expert who uses their technical knowledge to
overcome a problem. While "hacker" can refer to any skilled computer programmer, the
term has become associated in popular culture with a "security hacker", someone who, with
their technical knowledge, uses bugs or exploits to break into computer systems.
Two types of hackers, there are two definitions of the word "hacker":
White hat hacker :-White hats are hackers who work to keep data safe from other
hackers by finding system vulnerabilities that can be mitigated. White hats are
usually employed by the target system's owner and are typically paid (sometimes
quite well) for their work. Their work is not illegal because it is done with the system
owner's consent.
Black hat hacker :-Black hats or crackers are hackers with malicious intentions. They
often steal, exploit, and sell data, and are usually motivated by personal gain. Their
work is usually illegal. A cracker is like a black hat hacker, [13] but is specifically
someone who is very skilled and tries via hacking to make profits or to benefit, not
just to vandalize. Crackers find exploits for system vulnerabilities and often use them
to their advantage by either selling the fix to the system owner or selling the exploit
to other black hat hackers, who in turn use it to steal information or gain royalties.
Grey hat hacker :-Grey hats include those who hack for fun or to troll. They may
both fix and exploit vulnerabilities, but usually not for financial gain. Even if not
malicious, their work can still be illegal, if done without the target system owner's
consent, and grey hats are usually associated with black hat hackers.
The term is frequently attributed to Cult of the Dead Cow (cDc) member "Omega," who
used it in a 1996 e-mail to the group. [3][4] However, writer Jason Sack used the term earlier,
in a 1995 article on New Media artist Shu Lea Cheang. Due to the variety of meanings of its
root words, hacktivism is sometimes ambiguous and there exists significant disagreement
over the kinds of activities and purposes it encompasses. Some definitions include acts of
cyberterrorism while others simply reaffirm the use of technological hacking to effect social
change.[
3-cracker
A cracker is an individual who performs cracking, or the process of breaking into a computer
or a network system. A cracker might be performing cracking for malicious activities, profit,
for certain nonprofit intentions or causes, or just for a challenge. Some crackers break into a
network system deliberately to point out the flaws involved in that network's security
system. In most cases, crackers aim to gain access to confidential data, get hold of free
software applications, or carry out malicious damage to files.