Concrete security

This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these messages) This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. Find sources: "Concrete security" – news · newspapers · books · scholar · JSTOR (May 2021) (Learn how and when to remove this message) This article may be too technical for most readers to understand. Please help improve it to make it understandable to non-experts, without removing the technical details. (May 2021) (Learn how and when to remove this message) This article relies excessively on references to primary sources. Please improve this article by adding secondary or tertiary sources. Find sources: "Concrete security" – news · newspapers · books · scholar · JSTOR (May 2021) (Learn how and when to remove this message) (Learn how and when to remove this message)

In cryptography, concrete security or exact security is a practice-oriented approach that aims to give more precise estimates of the computational complexities of adversarial tasks than polynomial equivalence would allow.^{[citation needed]} It quantifies the security of a cryptosystem by bounding the probability of success for an adversary running for a fixed amount of time.^{[1][better source needed]} Security proofs with precise analyses are referred to as concrete.^{[2][better source needed]}

Traditionally, provable security is asymptotic: it classifies the hardness of computational problems using polynomial-time reducibility. Secure schemes are defined to be those in which the advantage of any computationally bounded adversary is negligible. While such a theoretical guarantee is important, in practice one needs to know exactly how efficient a reduction is because of the need to instantiate the security parameter - it is not enough to know that "sufficiently large" security parameters will do. An inefficient reduction results either in the success probability for the adversary or the resource requirement of the scheme being greater than desired.^{[citation needed]}

Concrete security parametrizes all the resources available to the adversary, such as running time and memory, and other resources specific to the system in question, such as the number of plaintexts it can obtain or the number of queries it can make to any oracles available. Then the advantage of the adversary is upper bounded as a function of these resources and of the problem size. It is often possible to give a lower bound (i.e. an adversarial strategy) matching the upper bound, hence the name exact security.^{[citation needed]}

Concrete security estimates have been applied to cryptographic algorithms:

• In 1996, schemes for digital signatures based on the RSA and Rabin cryptosystems were proposed, which were shown to be approximately as difficult to break as the original cryptosystems.^[3]
• In 1997, some notions of concrete security (left-or-right indistinguishability, real-or-random indistinguishability, find-then-guess security, and semantic-security) for symmetric encryption algorithms were proved approximately equivalent in various block cipher modes of operation such as CBC, CTR, and XOR (a stateless variant of CBC).^{[4][clarification needed]}
• In 2017, a thesis showed that lattice point enumeration and lattice block reduction algorithms could be used to attack lattice-based cryptography.^[5]
• In 2021, "guess-and-determine" and "guess-and-decode"-type attacks^{[clarification needed]} were demonstrated against a proposed pseudorandom generator in NC0, where instances with parameter values previously claimed to have 128-bit security were solved in about ${\displaystyle 2^{78}}$ operations.^{[6][better source needed]}

In addition, a software tool named the "Foundational Cryptography Framework", which embeds into Coq, is able to formally verify proofs of concrete security.^[7] For example, it is able to verify the concrete security of ElGamal encryption.^[7]

• https://www.cs.purdue.edu/homes/jblocki/courses/555_Fall18/slides/Week2.pdf
• https://crypto.stanford.edu/~dabo/cryptobook/draft_0_3.pdf
• https://eprint.iacr.org/2006/278.pdf
• https://www.baigneres.net/downloads/2007_provable_security.pdf
• https://eprint.iacr.org/2020/1213.pdf

This cryptography-related article is a stub. You can help Wikipedia by expanding it.

• v
• t
• e