human: Given a hyperedge-centered hypergraph: <hypergraph>, where the center hyperedge is induced by one source paper and its member nodes are the cited papers.

Details of the hypergraph:
Center hyperedge (induced by source paper "when good components go bad formally secure compilation despite dynamic compromise"):
  Abstract: We propose a new formal criterion for secure compilation, giving strong end-to-end security guarantees for software components written in unsafe, low-level languages with C-style undefined behavior. Our criterion is the first to model_dynamic_ compromise in a system of mutually distrustful components running with least privilege. Each component is protected from all the others---in particular, from components that have encountered undefined behavior and become compromised. Each component receives secure compilation guarantees up to the point when it becomes compromised, after which an attacker can take complete control over the component and use any of its privileges to attack the remaining uncompromised components. More precisely, we ensure that dynamically compromised components cannot break the safety properties of the system at the target level any more than equally privileged components without undefined behavior already could in the source language. #R##N#To illustrate this model, we build a secure compilation chain for an unsafe language with buffers, procedures, and components. We compile it to a simple RISC abstract machine with built-in compartmentalization and provide thorough proofs, many of them machine-checked in Coq, showing that the compiler satisfies our secure compilation criterion. Finally, we show that the protection guarantees offered by the compartmentalized abstract machine can be achieved at the machine-code level using either software fault isolation or a tag-based reference monitor.

Includes members:
  Member "journey beyond full abstraction exploring robust property preservation for secure compilation":
    also connected through other hyperedges:
      - Hyperedge HE-1 (induced by source paper "why should anyone use colours or syntax highlighting beyond code snippets")
  Member "robust hyperproperty preservation for secure compilation extended abstract":
    also connected through other hyperedges:
      - Hyperedge HE-2 (induced by source paper "robustly safe compilation or efficient provably secure compilation")
  Member "effectivesan type and memory error detection using dynamically typed c c":
    also connected through other hyperedges:
      - Hyperedge HE-3 (induced by source paper "dangkiller eliminating dangling pointers efficiently via implicit identifier")
  Member "the meaning of memory safety":
    also connected through other hyperedges:
      (none)
  Member "modular fully abstract compilation by approximate back translation":
    also connected through other hyperedges:
      - Hyperedge HE-4 (induced by source paper "robustly safe compilation or efficient provably secure compilation")
  Member "beyond good and evil formalizing the security guarantees of compartmentalizing compilation":
    also connected through other hyperedges:
      - Hyperedge HE-5 (induced by source paper "trace relating compiler correctness and secure compilation")
  Member "towards a fully abstract compiler using micro policies secure compilation for mutually distrustful components":
    also connected through other hyperedges:
      - Hyperedge HE-6 (induced by source paper "software fault isolation for robust compilation")

Question: Please tell me which class the source paper belongs to. The 40 classes are: cs.NA(Numerical Analysis), cs.MM(Multimedia), cs.LO(Logic in Computer Science), cs.CY(Computers and Society), cs.CR(Cryptography and Security), cs.DC(Distributed, Parallel, and Cluster Computing), cs.HC(Human-Computer Interaction), cs.CE(Computational Engineering, Finance, and Science), cs.NI(Networking and Internet Architecture), cs.CC(Computational Complexity), cs.AI(Artificial Intelligence), cs.MA(Multiagent Systems), cs.GL(General Literature), cs.NE(Neural and Evolutionary Computing), cs.SC(Symbolic Computation), cs.AR(Hardware Architecture), cs.CV(Computer Vision and Pattern Recognition), cs.GR(Graphics), cs.ET(Emerging Technologies), cs.SY(Systems and Control), cs.CG(Computational Geometry), cs.OH(Other Computer Science), cs.PL(Programming Languages), cs.SE(Software Engineering), cs.LG(Machine Learning), cs.SD(Sound), cs.SI(Social and Information Networks), cs.RO(Robotics), cs.IT(Information Theory), cs.PF(Performance), cs.CL(Computation and Language), cs.IR(Information Retrieval), cs.MS(Mathematical Software), cs.FL(Formal Languages and Automata Theory), cs.DS(Data Structures and Algorithms), cs.OS(Operating Systems), cs.GT(Computer Science and Game Theory), cs.DB(Databases), cs.DL(Digital Libraries), cs.DM(Discrete Mathematics). Directly output the class name.

gpt: cs.CR(Cryptography and Security)