Nov. 13, 2023, 2:10 a.m. | Matthew Kolosick, Basavesh Ammanaghatta Shivakumar, Sunjay Cauligi, Marco Patrignani, Marco Vassena, Ranjit Jhala, Deian Stefan

cs.CR updates on arXiv.org arxiv.org

The constant-time property is considered the security standard for
cryptographic code. Code following the constant-time discipline is free from
secret-dependent branches and memory accesses, and thus avoids leaking secrets
through cache and timing side-channels. The constant-time property makes a
number of implicit assumptions that are fundamentally at odds with the reality
of cryptographic code. Constant-time is not robust. The first issue with
constant-time is that it is a whole-program property: It relies on the entirety
of the code base being …

cache code cryptographic cryptography discipline free memory property reality secret secrets security security standard standard

Enterprise Security Architect

@ Proofpoint | Utah

Senior Incident Response and Digital Forensics Engineer

@ Danske Bank | Vilnius, Lithuania

SOC Analyst (Remote)

@ Bertelsmann | New York City, US, 10019

Risk Consulting - Protect Tech - Staff - IT Compliance - ISO-NIST-FISMA-PCI DSS and Privacy

@ EY | Bengaluru, KA, IN, 560016

Security Officer Warrenpoint Harbour

@ TSS | Newry, County Down, United Kingdom

Senior DevSecOps Engineer

@ Scientific Systems Company, Inc. | Burlington, Massachusetts, United States