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: "meltdownprime and spectreprime automatically synthesized attacks exploiting invalidation based coherence protocols"
  Abstract: The recent Meltdown and Spectre attacks highlight the importance of automated verification techniques for identifying hardware security vulnerabilities. We have developed a tool for synthesizing microarchitecture-specific programs capable of producing any user-specified hardware execution pattern of interest. Our tool takes two inputs: a formal description of (i) a microarchitecture in a domain-specific language, and (ii) a microarchitectural execution pattern of interest, e.g. a threat pattern. All programs synthesized by our tool are capable of producing the specified execution pattern on the supplied microarchitecture. #R##N#We used our tool to specify a hardware execution pattern common to Flush+Reload attacks and automatically synthesized security litmus tests representative of those that have been publicly disclosed for conducting Meltdown and Spectre attacks. We also formulated a Prime+Probe threat pattern, enabling our tool to synthesize a new variant of each---MeltdownPrime and SpectrePrime. Both of these new exploits use Prime+Probe approaches to conduct the timing attack. They are both also novel in that they are 2-core attacks which leverage the cache line invalidation mechanism in modern cache coherence protocols. These are the first proposed Prime+Probe variants of Meltdown and Spectre. But more importantly, both Prime attacks exploit invalidation-based coherence protocols to achieve the same level of precision as a Flush+Reload attack. While mitigation techniques in software (e.g., barriers that prevent speculation) will likely be the same for our Prime variants as for original Spectre and Meltdown, we believe that hardware protection against them will be distinct. As a proof of concept, we implemented SpectrePrime as a C program and ran it on an Intel x86 processor, averaging about the same accuracy as Spectre over 100 runs---97.9% for Spectre and 99.95% for SpectrePrime.

Connected through hyperedge HE-1 (induced by source paper "store to leak forwarding leaking data on meltdown resistant cpus"):
  with members:
    - "practical enclave malware with intel sgx"
    - "smotherspectre exploiting speculative execution through port contention"
    - "page cache attacks"
    - "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-2 (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"
    - "spectre attacks exploiting speculative execution"

Connected through hyperedge HE-3 (induced by source paper "revisiting and evaluating software side channel vulnerabilities and countermeasures in cryptographic applications"):
  with members:
    - "when human cognitive modeling meets pins user independent inter keystroke timing attacks"
    - "identifying cache based side channels through secret augmented abstract interpretation"
    - "sgxpectre stealing intel secrets from sgx enclaves via speculative execution"
    - "spoiler speculative load hazards boost rowhammer and cache attacks"
    - "verifying and synthesizing constant resource implementations with types"
    - "spectre attacks exploiting speculative execution"
    - "robust website fingerprinting through the cache occupancy channel"
    - "a systematic evaluation of transient execution attacks and defenses"

Connected through hyperedge HE-4 (induced by source paper "leaking information through cache lru states"):
  with members:
    - "memjam a false dependency attack against constant time crypto implementations"
    - "smotherspectre exploiting speculative execution through port contention"
    - "reload refresh abusing cache replacement policies to perform stealthy cache attacks"
    - "netspectre read arbitrary memory over network"
    - "safespec banishing the spectre of a meltdown with leakage free speculation"
    - "spectre attacks exploiting speculative execution"
    - "spectre returns speculation attacks using the return stack buffer"
    - "ret2spec speculative execution using return stack buffers"

Connected through hyperedge HE-5 (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"
    - "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"
    - "oo7 low overhead defense against spectre attacks via binary analysis"
    - "ret2spec speculative execution using return stack buffers"

Connected through hyperedge HE-6 (induced by source paper "safespec banishing the spectre of a meltdown with leakage free speculation"):
  with members:
    - "speculative buffer overflows attacks and defenses"
    - "spectre attacks exploiting speculative execution"
    - "you shall not bypass employing data dependencies to prevent bounds check bypass"
    - "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"

Connected through hyperedge HE-7 (induced by source paper "netspectre read arbitrary memory over network"):
  with members:
    - "spectre attacks exploiting speculative execution"
    - "speculose analyzing the security implications of speculative execution in cpus"
    - "automated detection exploitation and elimination of double fetch bugs using modern cpu features"
    - "inferring fine grained control flow inside sgx enclaves with branch shadowing"
    - "armageddon cache attacks on mobile devices"
    - "airhopper bridging the air gap between isolated networks and mobile phones using radio frequencies"

Connected through hyperedge HE-8 (induced by source paper "spectre returns speculation attacks using the return stack buffer"):
  with members:
    - "safespec banishing the spectre of a meltdown with leakage free speculation"
    - "spectre attacks exploiting speculative execution"
    - "speculose analyzing the security implications of speculative execution in cpus"
    - "inferring fine grained control flow inside sgx enclaves with branch shadowing"

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)