Which one of the following is not a security protocol ?
- (a)TLS
- (b)SSL
- (c)IPsec
- (d)MIME
Correct — D, (d) MIME. MIME stands for Multipurpose Internet Mail Extensions, and it is a content-formatting standard, not a security protocol. It was written to solve a problem that has nothing to do with secrecy: the original Internet mail format could carry only plain seven-bit ASCII text, so an English letter travelled fine while an attached image, a spreadsheet, a Devanagari message or an accented European name did not. MIME adds header fields — Content-Type, Content-Transfer-Encoding, and the multipart boundaries that let one message carry a body and several attachments — which tell the receiving program what each part of the message is and how it was encoded for transit. It encrypts nothing, authenticates nobody and detects no tampering. The other three options are all genuine security protocols, and the item is a straight elimination: TLS and SSL secure a connection at the transport layer, IPsec secures traffic at the network layer, and MIME describes the shape of a message's content. So MIME is the odd one out and the keyed answer. The reason MIME is a good distractor — and the reason a candidate should hold the distinction firmly — is that there is a security protocol with almost the same name. S/MIME, Secure/Multipurpose Internet Mail Extensions, sits on top of MIME and does add security: it signs a message with the sender's private key so the recipient can verify who sent it and that nothing was altered, and it encrypts the body so only the holder of the matching private key can read it, using X.509 certificates issued by a certifying authority. The 'S' is doing all the security work. MIME by itself is the envelope-and-labelling scheme; S/MIME is the sealed envelope. The paper prints MIME without the prefix, and that is the whole point of the option. The same MIME type labels were later borrowed by the web, which is why a web server announces a page as text/html or an image as image/png. That reuse makes MIME even more visible in everyday computing and even easier to mistake for something protective.
- (a)TLS — TLS, Transport Layer Security, is a security protocol, so it cannot answer a question asking which one is not. It sits between the transport layer and the application and gives a connection three things: confidentiality through encryption of the data in transit, integrity through a message authentication check that detects alteration, and authentication of the server (and optionally the client) through certificates. It is what the 's' in HTTPS stands for, and it also secures mail submission, file transfer and many other application protocols. The IETF standardised TLS 1.0 in 1999 as the successor to SSL 3.0; the current version in general use is TLS 1.3.
- (b)SSL — SSL, Secure Sockets Layer, is also a security protocol — indeed it is the ancestor of TLS. It was designed at Netscape in the mid-1990s to protect data between a browser and a web server, and versions 2.0 and 3.0 were the first widely deployed way of encrypting web traffic. Both versions have since been formally deprecated because of discovered weaknesses, so a modern system that says 'SSL' is almost always running TLS under an old name. Deprecated is not the same as 'not a security protocol', and the option is wrong on the question as asked.
- (c)IPsec — IPsec, Internet Protocol Security, is a suite of security protocols and again cannot be the answer. It works one layer lower than TLS, at the network layer, and therefore protects every packet between two endpoints regardless of which application produced it. Its two protective headers are the Authentication Header, which gives integrity and origin authentication, and the Encapsulating Security Payload, which adds encryption; keys are negotiated by the Internet Key Exchange. It runs in transport mode, which protects the payload of a packet, or in tunnel mode, which wraps the whole original packet inside a new one — the mode that builds a virtual private network.
Network protocols are best sorted by the layer they act on and the job they do. MIME is a presentation-level convention about the FORM of a message's content: what type each part is, how it was encoded so that it survives a text-only transport, and where one part ends and the next begins. Security protocols do a different job — they provide some combination of confidentiality (nobody in between can read it), integrity (nobody in between can change it undetected), authentication (the other end is who it claims to be) and non-repudiation (the sender cannot later deny sending it). Where a security protocol sits decides what it can protect. IPsec sits at the network layer and secures everything travelling between two hosts or two gateways, transparently to the applications. TLS, and SSL before it, sit above the transport layer and secure one application's connection at a time, which is why a browser can show a padlock for one site and not another. S/MIME and PGP sit at the application layer and secure the message itself, so it stays protected while it rests in a mailbox rather than only while it is in flight. A candidate who can place a name on that ladder can usually answer this family of questions without having memorised anything else about the protocol.
The computers block of the EO/AO paper repeatedly asks the candidate to sort a list of familiar acronyms into the one that does not belong, and the discrimination is almost always between a protocol's purpose rather than its internals. The habit rewarded here is expanding the acronym before choosing: 'Transport Layer Security' and 'Internet Protocol Security' both announce their purpose in their own names, and 'Multipurpose Internet Mail Extensions' announces something else entirely. Note also that the booklet prints a space before the question mark, which is this paper's house style throughout, and the word 'not' is printed in bold italics so that the negative ask is hard to miss.
- MIME (Multipurpose Internet Mail Extensions) formats and labels message content; it provides no encryption, no integrity check and no authentication.
- S/MIME is the secure variant: it signs and encrypts message bodies using X.509 certificates, and the security is entirely in the 'S'.
- SSL was developed at Netscape in the mid-1990s; TLS is its IETF successor, and SSL 2.0 and 3.0 are deprecated.
- TLS operates above the transport layer and secures one application connection; it is the 'S' of HTTPS.
- IPsec operates at the network layer and protects all traffic between endpoints, using the Authentication Header and the Encapsulating Security Payload.
- IPsec tunnel mode wraps a whole packet inside a new one and is the basis of most virtual private networks.
- MIME's Content-Type labels were later adopted by the web as media types, such as text/html and image/png.
- The four services a security protocol may provide are confidentiality, integrity, authentication and non-repudiation.
- Reading MIME as S/MIME because the two names differ by one letter — only the latter is a security protocol.
- Assuming SSL is not a security protocol because it is obsolete; deprecation does not change what a protocol was designed to do.
- Treating TLS and SSL as two unrelated things rather than successive versions of one design.
- Missing that the ask is negative — the word 'not' is set in bold italics precisely because three of the four options are correct statements.
Security and networking acronyms recur in the EO/AO computers block in three shapes: an odd-one-out like this one, a direct 'what does X stand for', and a matching item pairing a protocol with its layer or its port number. Build a single table of the two dozen acronyms an office user meets — HTTP, HTTPS, FTP, SMTP, POP3, IMAP, TCP, UDP, IP, DNS, DHCP, TLS, SSL, IPsec, MIME, S/MIME, PGP — with the expansion, the layer and the one-line purpose of each, and most of the family becomes answerable on sight.
No directly related past PYQ was found.
- practice — not a real PYQ
Which one of the following provides security at the network layer ?
- (a)TLS
- (b)S/MIME
- (c)IPsec
- (d)PGP
Answer(c) IPsec
- practice — not a real PYQ
The primary purpose of MIME in electronic mail is to :
- (a)Encrypt the contents of a message
- (b)Allow a message to carry non-ASCII text and attachments
- (c)Authenticate the sender of a message
- (d)Compress a message before transmission
Answer(b) Allow a message to carry non-ASCII text and attachments