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: "you shall not bypass employing data dependencies to prevent bounds check bypass"
  Abstract: A recent discovery of a new class of microarchitectural attacks called Spectre picked up the attention of the security community as these attacks can overcome many traditional mechanisms of defense, such as bounds checking. One of the attacks - Bounds Check Bypass - can neither be efficiently solved on system nor architectural levels, and requires changes in the application itself. So far, the proposed mitigations involved serialization, which reduces the usage of CPU resources and causes high overheads. In this work, we propose a method of only delaying the vulnerable instructions, without the necessity to completely serialize execution. Our prototype implemented as an LLVM pass causes 60% overhead across Phoenix benchmark suite, which compares favorably to the full serialization causing 440% slowdown.

Connected through hyperedge HE-1 (induced by source paper "context leakage free transient execution"):
  with members:
    - "fallout reading kernel writes from user space"
    - "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"
    - "speculative buffer overflows attacks and defenses"
    - "netspectre read arbitrary memory over network"
    - "safespec banishing the spectre of a meltdown with leakage free speculation"
    - "meltdownprime and spectreprime automatically synthesized attacks exploiting invalidation based coherence protocols"

Connected through hyperedge HE-2 (induced by source paper "speccfi mitigating spectre attacks using cfi informed speculation"):
  with members:
    - "context leakage free transient execution"
    - "smotherspectre exploiting speculative execution through port contention"
    - "store to leak forwarding leaking data on meltdown resistant cpus"
    - "zombieload cross privilege boundary data sampling"
    - "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"

Connected through hyperedge HE-3 (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"
    - "spectector principled detection of speculative information flows"
    - "spectre attacks exploiting speculative execution"
    - "spectre returns speculation attacks using the return stack buffer"

Connected through hyperedge HE-4 (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"
    - "spectector principled detection of speculative information flows"
    - "journey beyond full abstraction exploring robust property preservation for secure compilation"
    - "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-5 (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"
    - "spectector principled detection of speculative information flows"
    - "spectre attacks exploiting speculative execution"
    - "oo7 low overhead defense against spectre attacks via binary analysis"
    - "a systematic evaluation of transient execution attacks and defenses"

Connected through hyperedge HE-6 (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"
    - "spectector principled detection of speculative information flows"
    - "spectre attacks exploiting speculative execution"
    - "spectre returns speculation attacks using the return stack buffer"

Connected through hyperedge HE-7 (induced by source paper "spectector principled detection of speculative information flows"):
  with members:
    - "spectre is here to stay an analysis of side channels and speculative execution"
    - "sgxpectre stealing intel secrets from sgx enclaves via speculative execution"
    - "netspectre read arbitrary memory over network"
    - "meltdownprime and spectreprime automatically synthesized attacks exploiting invalidation based coherence protocols"
    - "spectre attacks exploiting speculative execution"
    - "spectre returns speculation attacks using the return stack buffer"
    - "oo7 low overhead defense against spectre attacks via binary analysis"
    - "ret2spec speculative execution using return stack buffers"

Connected through hyperedge HE-8 (induced by source paper "safespec banishing the spectre of a meltdown with leakage free speculation"):
  with members:
    - "speculative buffer overflows attacks and defenses"
    - "meltdownprime and spectreprime automatically synthesized attacks exploiting invalidation based coherence protocols"
    - "spectre attacks exploiting speculative execution"
    - "speculose analyzing the security implications of speculative execution in cpus"
    - "spectre returns speculation attacks using the return stack buffer"
    - "ret2spec speculative execution using return stack buffers"
    - "a systematic evaluation of transient execution attacks and defenses"
    - "lazyfp leaking fpu register state using microarchitectural side channels"

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)