ArticleslgStudy

computer science

Provable security

Provable security is a computer science topic covered in the lgStudy science library. This page brings together a partial reference excerpt, illustrations, worked examples, real-world applications and a short study plan, so you can understand Provable security rather than just read about it. In short: Provable security refers to any type or level of computer security that can be proved. It is used in different ways by different fields.

Key takeaways

  • Provable security belongs to computer science; place it in that map before memorising details.
  • Learn the definition first, then one example that makes the definition concrete.
  • Connect Provable security to a quantity you can measure, compute or draw — that is where exam questions come from.
  • Reproduce the core statement of Provable security from memory before moving on to harder problems.

Reference excerpt

Provable security refers to any type or level of computer security that can be proved. It is used in different ways by different fields. Usually, this refers to mathematical proofs, which are common in cryptography. In such a proof, the capabilities of the attacker are defined by an adversarial model (also referred to as attacker model): the aim of the proof is to show that the attacker must solve the underlying hard problem in order to break the security of the modelled system. Such a proof generally does not consider side-channel attacks or other implementation-specific attacks because they are usually impossible to model without implementing the system(and so the proof applies only to this implementation. Outside cryptography, the term is often used in conjunction with secure coding and security by design, both of which can rely on proofs to show the security of a particular approach. As with the cryptographic setting, this involves an attacker model and a model of the system. For example, code can be verified to match the intended functionality, described by a model: this can be done through static checking. Both techniques are sometimes used for evaluating products (see Common Criteria): the security here depends not only on the correctness of the attacker model but also on the model of the code. Finally, the term provable security is sometimes used by sellers of security software that are attempting to sell security products like firewalls, antivirus software and intrusion detection systems. As these products are typically not subject to scrutiny, many security researchers consider this type of claim to be selling snake oil.

In cryptography In cryptography, a system has provable security if its security requirements can be stated formally in an adversarial model, as opposed to heuristically, with clear assumptions that the adversary has access to the system as well as enough computational resources. The proof of security (called a "reduction") is that the security requirements are met provided the assumptions about the adversary's access to the system are satisfied, and some clearly-stated assumptions about the hardness of certain computational tasks hold. An early example of such requirements and proof was given by Goldwasser and Micali for semantic security and the construction based on the quadratic residuosity problem. Some proofs of security are in given theoretical models such as the random oracle model, where real cryptographic hash functions are represented by an idealization. There are several lines of research in provable security. One is to establish the "correct" definition of security for a given, intuitively understood task. Another is to suggest constructions and proofs based on general assumptions as much as possible, for instance the existence of a one-way function. A major open problem is to establish such proofs based on P ≠ NP, since the existence of one-way functions is not known to follow from the P ≠ NP conjecture.

Controversies Several researchers have found mathematical fallacies in proofs that had been used to make claims about the security of important protocols. In the following partial list of such researchers, their names are followed by first a reference to the original paper with the purported proof and then a reference to the paper in which the researchers reported on flaws: V. Shoup; A. J. Menezes; A. Jha and M. Nandi; D. Galindo; T. Iwata, K. Ohashi, and K. Minematsu; M. Nandi; J.-S. Coron and D. Naccache; D. Chakraborty, V. Hernández-Jiménez, and P. Sarkar; P. Gaži and U. Maurer; S. A. Kakvi and E. Kiltz; and T. Holenstein, R. Künzler, and S. Tessaro. Koblitz and Menezes have written that provable security results for important cryptographic protocols frequently have fallacies in the proofs; are often interpreted in a misleading manner, which gives false assurances; typically rely upon strong assumptions that may turn out to be false; are based on unrealistic models of security; and serve to distract researchers' attention from the need for "old-fashioned" (non-mathematical) testing and analysis. Their series of papers supporting those claims have been controversial in the community. Among the researchers who have rejected the viewpoint of Koblitz–Menezes is Oded Goldreich, a leading theoretician and author of Foundations of Cryptography. He wrote a refutation of their first paper "Another look at 'provable security'" that he titled "On post-modern cryptography". Goldreich wrote: "... we point out some of the fundamental philosophical flaws that underlie the said article and some of its misconceptions regarding theoretical research in cryptography in the last quarter of a century." In his essay Goldreich argued that the rigorous analysis methodology of provable security is the only one compatible with science, and that Koblitz and Menezes are "reactionary (i.e., they play to the hands of the opponents of progress)". In 2007, Koblitz published "The Uneasy Relationship Between Mathematics and Cryptography", which contained some controversial statements about provable security and other topics. Researchers Oded Goldreich, Boaz Barak, Jonathan Katz, Hugo Krawczyk, and Avi Wigderson wrote letters responding to Koblitz's article, which were published in the November 2007 and January 2008 issues of the journal. Katz, who is coauthor of a highly regarded cryptography textbook, called Koblitz's article "snobbery at its purest"; and Wigderson, who is a permanent member of the Institute for Advanced Study in Princeton, accused Koblitz of "slander". Ivan Damgård later wrote a position paper at ICALP 2007 on the technical issues, and it was recommended by Scott Aaronson as a good in-depth analysis. Brian Snow, former Technical Director of the Information Assurance Directorate of the U.S. National Security Agency, recommended the Koblitz-Menezes paper "The brave new world of bodacious assumptions in cryptography" to the audience at the RSA Conference 2010 Cryptographers Panel.

… excerpt ends here. Continue reading the full article.

Worked examples

Example 1 — a first encounter with Provable security

Start with the simplest possible case. Write down what Provable security claims or describes in one sentence, then invent the smallest concrete situation in which that sentence is true. In computer science, the smallest case is usually a single object, a single equation or a single measurement. Check that every symbol or term in your sentence has a meaning in that case.

Example 2 — changing one variable

Take the situation from Example 1 and change exactly one quantity: double it, halve it, or set it to zero. Predict what should happen to Provable security before you calculate. Comparing your prediction with the result is the fastest way to find out whether you understand the idea or only the words.

Example 3 — an exam-style question

Typical questions about Provable security ask you to (a) state it precisely, (b) apply it to given data, and (c) explain a limitation. Practise writing all three answers in under five minutes; the third part is what separates a full-mark answer from an average one.

Applications of Provable security

In research
Provable security appears in computer science research whenever the underlying quantities have to be modelled precisely. Papers usually cite it as a starting assumption and then explore where it breaks down.
In technology and industry
Engineering practice reuses Provable security in design rules, simulations and safety margins. Knowing the idea lets you read a specification sheet and understand why the numbers look the way they do.
In the classroom
Provable security is common in secondary-school and first-year university syllabi. It links to neighbouring topics Theory of cryptography, so understanding it makes those chapters shorter.
In everyday life
Look for Provable security outside the textbook — in sport, cooking, traffic, electronics or the sky above you. An example you found yourself is remembered far longer than one you were given.

Affiliate

Preply — study more efficiently by working with a personal tutor. 50% off.

How to study Provable security in 20 minutes

  1. Read the reference excerpt below once, without taking notes.
  2. Close the page and write down what Provable security means in your own words.
  3. Compare your version with the excerpt and mark what you missed.
  4. Work through the three examples above with pen and paper.
  5. Explain Provable security out loud to somebody else — or to Teacher Smith in the lgStudy chat.

Frequently asked questions

What is Provable security in simple terms?

Provable security refers to any type or level of computer security that can be proved. It is used in different ways by different fields.

Why does Provable security matter?

Because it connects several computer science ideas at once: it gives you a definition you can apply, a quantity you can calculate, and a way to check whether a result is plausible.

How should I study Provable security?

Read the excerpt, restate it from memory, then work through the examples and applications listed on this page. The five-step study plan above takes about twenty minutes.

What does this page cover?

It gives you a compact reference excerpt plus original lgStudy explanations, examples, applications and study material on Provable security.

Tags

  • Theory of cryptography

Keep exploring