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: "pac it up towards pointer integrity using arm pointer authentication"
  Abstract: Run-time attacks against programs written in memory-unsafe programming languages (e.g., C and C++) remain a prominent threat against computer systems. The prevalence of techniques like return-oriented programming (ROP) in attacking real-world systems has prompted major processor manufacturers to design hardware-based countermeasures against specific classes of run-time attacks. An example is the recently added support for pointer authentication (PA) in the ARMv8-A processor architecture, commonly used in devices like smartphones. PA is a low-cost technique to authenticate pointers so as to resist memory vulnerabilities. It has been shown to enable practical protection against memory vulnerabilities that corrupt return addresses or function pointers. However, so far, PA has received very little attention as a general purpose protection mechanism to harden software against various classes of memory attacks. In this paper, we use PA to build novel defenses against various classes of run-time attacks, including the first PA-based mechanism for data pointer integrity. We present PARTS, an instrumentation framework that integrates our PA-based defenses into the LLVM compiler and the GNU/Linux operating system and show, via systematic evaluation, that PARTS provides better protection than current solutions at a reasonable performance overhead

Connected through hyperedge HE-1 (induced by source paper "using name confusion to enhance security"):
  with members:
    - "block oriented programming automating data only attacks"
    - "cfi care hardware supported call and return enforcement for commercial microcontrollers"
    - "control flow integrity precision security and performance"

Connected through hyperedge HE-2 (induced by source paper "ptauth temporal memory safety via robust points to authentication"):
  with members:
    - "memory tagging and how it improves c c memory safety"
    - "cup comprehensive user space protection for c c"
    - "freeguard a faster secure heap allocator"

Connected through hyperedge HE-3 (induced by source paper "sok hardware security support for trustworthy execution"):
  with members:
    - "secloak arm trustzone based mobile peripheral control"
    - "reverse engineering x86 processor microcode"
    - "extracting secrets from encrypted virtual machines"
    - "sgxpectre stealing intel secrets from sgx enclaves via speculative execution"
    - "spectre attacks exploiting speculative execution"
    - "lord of the x86 rings a portable user mode privilege separation architecture on x86"
    - "severed subverting amd s virtual machine encryption"
    - "a survey of hardware based control flow integrity cfi"

Connected through hyperedge HE-4 (induced by source paper "pacstack an authenticated call stack"):
  with members:
    - "dr sgx automated and adjustable side channel protection for sgx using data location randomization"
    - "shining light on shadow stacks"
    - "cfi care hardware supported call and return enforcement for commercial microcontrollers"
    - "cryptographically enforced control flow integrity"

Connected through hyperedge HE-5 (induced by source paper "pairs control flow protection using phantom addressed instructions"):
  with members:
    - "debloating software through piece wise compilation and loading"
    - "cfi care hardware supported call and return enforcement for commercial microcontrollers"

Connected through hyperedge HE-6 (induced by source paper "camouflage hardware assisted cfi for the arm linux kernel"):
  with members:
    - "protecting the stack with paced canaries"

Connected through hyperedge HE-7 (induced by source paper "arm pointer authentication based forward edge and backward edge control flow integrity for kernels"):
  with members:
    - "protecting the stack with paced canaries"

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)