Security policy compliance cannot be verified programmatically
Security policy compliance cannot be verified programmatically: a task in LegoFlow-SWE (Harbor dataset). Security policies in s2n‑tls that claim conformance to a standard (e.g. FIPS, perfect forward secrecy) are currently defined by manually assembling lists of allowed ciphers and signatures…
The task
Security policies in s2n‑tls that claim conformance to a standard (e.g. FIPS, perfect forward secrecy) are currently defined by manually assembling lists of allowed ciphers and signatures. There is no automated, code‑driven way to check that a policy actually adheres to a given set of rules.
Part of Lego-X/LegoFlow-SWE.