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: "sprobes enforcing kernel code integrity on the trustzone architecture"
  Abstract: Many smartphones now deploy conventional operating systems, so the rootkit attacks so prevalent on desktop and server systems are now a threat to smartphones. While researchers have advocated using virtualization to detect and prevent attacks on operating systems (e.g., VM introspection and trusted virtual domains), virtualization is not practical on smartphone systems due to the lack of virtualization support and/or the expense of virtualization. Current smartphone processors do have hardware support for running a protected environment, such as the ARM TrustZone extensions, but such hardware does not control the operating system operations sufficiently to enable VM introspection. In particular, a conventional operating system running with TrustZone still retains full control of memory management, which a rootkit can use to prevent traps on sensitive instructions or memory accesses necessary for effective introspection. In this paper, we present SPROBES, a novel primitive that enables introspection of operating systems running on ARM TrustZone hardware. Using SPROBES, an introspection mechanism protected by TrustZone can instrument individual operating system instructions of its choice, receiving an unforgeable trap whenever any SPROBE is executed. The key challenge in designing SPROBES is preventing the rootkit from removing them, but we identify a set of five invariants whose enforcement is sufficient to restrict rootkits to execute only approved, SPROBE-injected kernel code. We implemented a proof-of-concept version of SPROBES for the ARM Fast Models emulator, demonstrating that in Linux kernel 2.6.38, only 12 SPROBES are sufficient to enforce all five of these invariants. With SPROBES we show that it is possible to leverage the limited TrustZone extensions to limit conventional kernel execution to approved code comprehensively.

Connected through hyperedge HE-1 (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"
    - "pac it up towards pointer integrity using arm pointer authentication"
    - "lord of the x86 rings a portable user mode privilege separation architecture on x86"
    - "severed subverting amd s virtual machine encryption"

Connected through hyperedge HE-2 (induced by source paper "scanclave verifying application runtime integrity in untrusted environments"):
  with members:
    - "practical enclave malware with intel sgx"
    - "integrating remote attestation with transport layer security"
    - "software grand exposure sgx cache attacks are practical"

Connected through hyperedge HE-3 (induced by source paper "let the cloud watch over your iot file systems"):
  with members:
    - "a robust real time automatic license plate recognition based on the yolo detector"
    - "trustshadow secure execution of unmodified applications with arm trustzone"

Connected through hyperedge HE-4 (induced by source paper "trustshadow secure execution of unmodified applications with arm trustzone"):
  with members:
    - "fog assisted wiot a smart fog gateway for end to end analytics in wearable internet of things"
    - "armageddon cache attacks on mobile devices"

Connected through hyperedge HE-5 (induced by source paper "secure containers in android the samsung knox case study"):
  with members:
    - "evaluation of security solutions for android systems"

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)