human: Given a node-centered hypergraph: <hypergraph>, where nodes represent papers and hyperedges represent sets of papers co-cited by a source paper.

Details of the hypergraph:
Center node: "spectector principled detection of speculative information flows"
  Abstract: Since the advent of SPECTRE, a number of countermeasures have been proposed and deployed. Rigorously reasoning about their effectiveness, however, requires a well-defined notion of security against speculative execution attacks, which has been missing until now. In this paper (1) we put forward speculative non-interference, the first semantic notion of security against speculative execution attacks, and (2) we develop SPECTECTOR, an algorithm based on symbolic execution to automatically prove speculative non-interference, or to detect violations. We implement SPECTECTOR in a tool, which we use to detect subtle leaks and optimizations opportunities in the way major compilers place SPECTRE countermeasures. A scalability analysis indicates that checking speculative non-interference does not exhibit fundamental bottlenecks beyond those inherited by symbolic execution.

Connected through hyperedge HE-1 (induced by source paper "specusym speculative symbolic execution for cache timing leak detection"):
  with members:
    - "mitigating power side channels during compilation"
    - "specfuzz bringing spectre type vulnerabilities to the surface"
    - "identifying cache based side channels through secret augmented abstract interpretation"
    - "neural network model extraction attacks in edge devices by hearing architectural hints"
    - "abstract interpretation under speculative execution"
    - "ct fuzz fuzzing for timing leaks"
    - "savior towards bug driven hybrid testing"
    - "spoiler speculative load hazards boost rowhammer and cache attacks"

Connected through hyperedge HE-2 (induced by source paper "zombieload cross privilege boundary data sampling"):
  with members:
    - "smotherspectre exploiting speculative execution through port contention"
    - "fallout reading kernel writes from user space"
    - "store to leak forwarding leaking data on meltdown resistant cpus"
    - "spoiler speculative load hazards boost rowhammer and cache attacks"
    - "speculative buffer overflows attacks and defenses"
    - "netspectre read arbitrary memory over network"
    - "spectre attacks exploiting speculative execution"
    - "spectre returns speculation attacks using the return stack buffer"

Connected through hyperedge HE-3 (induced by source paper "towards constant time foundations for the new spectre era"):
  with members:
    - "abstract interpretation under speculative execution"
    - "spectre is here to stay an analysis of side channels and speculative execution"
    - "store to leak forwarding leaking data on meltdown resistant cpus"
    - "zombieload cross privilege boundary data sampling"
    - "spoiler speculative load hazards boost rowhammer and cache attacks"
    - "inspectre breaking and fixing microarchitectural vulnerabilities by formal analysis"
    - "eliminating timing side channel leaks using program repair"
    - "speculative buffer overflows attacks and defenses"

Connected through hyperedge HE-4 (induced by source paper "inspectre breaking and fixing microarchitectural vulnerabilities by formal analysis"):
  with members:
    - "towards constant time foundations for the new spectre era"
    - "spectre is here to stay an analysis of side channels and speculative execution"
    - "sgxpectre stealing intel secrets from sgx enclaves via speculative execution"
    - "zombieload cross privilege boundary data sampling"
    - "kleespectre detecting information leakage through speculative cache attacks via symbolic execution"
    - "speculative buffer overflows attacks and defenses"
    - "spectre attacks exploiting speculative execution"
    - "spectre returns speculation attacks using the return stack buffer"

Connected through hyperedge HE-5 (induced by source paper "specfuzz bringing spectre type vulnerabilities to the surface"):
  with members:
    - "context leakage free transient execution"
    - "specusym speculative symbolic execution for cache timing leak detection"
    - "spectre is here to stay an analysis of side channels and speculative execution"
    - "netspectre read arbitrary memory over network"
    - "safespec banishing the spectre of a meltdown with leakage free speculation"
    - "spectre attacks exploiting speculative execution"
    - "you shall not bypass employing data dependencies to prevent bounds check bypass"
    - "spectre returns speculation attacks using the return stack buffer"

Connected through hyperedge HE-6 (induced by source paper "exorcising spectres with secure compilers"):
  with members:
    - "towards constant time foundations for the new spectre era"
    - "speculative buffer overflows attacks and defenses"
    - "journey beyond full abstraction exploring robust property preservation for secure compilation"
    - "you shall not bypass employing data dependencies to prevent bounds check bypass"
    - "spectre returns speculation attacks using the return stack buffer"
    - "ret2spec speculative execution using return stack buffers"
    - "a formally verified compiler back end"

Connected through hyperedge HE-7 (induced by source paper "kleespectre detecting information leakage through speculative cache attacks via symbolic execution"):
  with members:
    - "abstract interpretation under speculative execution"
    - "symbolic verification of cache side channel freedom"
    - "spectre attacks exploiting speculative execution"
    - "you shall not bypass employing data dependencies to prevent bounds check bypass"
    - "oo7 low overhead defense against spectre attacks via binary analysis"
    - "a systematic evaluation of transient execution attacks and defenses"

Connected through hyperedge HE-8 (induced by source paper "a systematic evaluation of transient execution attacks and defenses"):
  with members:
    - "smotherspectre exploiting speculative execution through port contention"
    - "spoiler speculative load hazards boost rowhammer and cache attacks"
    - "speculative buffer overflows attacks and defenses"
    - "netspectre read arbitrary memory over network"
    - "safespec banishing the spectre of a meltdown with leakage free speculation"
    - "spectre attacks exploiting speculative execution"
    - "you shall not bypass employing data dependencies to prevent bounds check bypass"
    - "spectre returns speculation attacks using the return stack buffer"

Question: Please tell me which class the center node 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)