Controlling the What and Where of Declassification in Language-Based Security
From MaRDI portal
Recommendations
Cited in
(9)- Automated enforcement for relaxed information release with reference points
- Scheduler-independent declassification
- Attacker control and impact for confidentiality and integrity
- A semantic framework for declassification and endorsement
- Who Can Declassify?
- Programming Languages and Systems
- Programming Languages and Systems
- Relative security: (dis)proving resilience against semantic optimization vulnerabilities in Isabelle/HOL. Extended version
- Concurrent -hyperproperties
This page was built for publication: Controlling the What and Where of Declassification in Language-Based Security
Report a bug (only for logged in users!)Click here to report a bug for this page (MaRDI item Q5756493)