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: "toward a research software security maturity model"
  Abstract: In its Vision and Strategy for Software for Science, Engineering, and Education the NSF states that it will invest in activities that: "Recognize that software strategies must include the secure and reliable deployment and operation of services, for example by campuses or national facilities or industry, where identity, authentication, authorization and assurance are crucial operational capabilities." and "Result in high-quality, usable, secure, vulnerability-free, sustainable, robust, well-tested, and maintainable/evolvable software; and which promotes the sustainability of solid and useful on-going investments." #R##N#Such statements evidence that security should indeed be a first-class consideration of the software ecosystem. In this position paper, we share some thoughts related to research software security. Our thoughts are based on the observation that security is not a binary, all-or-nothing attribute, but a range of practices and requirements depending on how the software is expected to be deployed and used. We propose that the community leverage the concept of a maturity model, and work to agree on a research software security maturity model. This model would categorize different sets of security needs of the deployment community, and provide software developers a roadmap for advancing the security maturity of their software. The intent of this paper is not to express such a comprehensive maturity model, but instead to start a conversation and set some initial requirements.

Connected through hyperedge HE-1 (induced by source paper "summary of the first workshop on sustainable software for science practice and experiences wssspe1"):
  with members:
    - "experiences from software engineering of large scale amr multiphysics code frameworks"
    - "software abstractions and methodologies for hpc simulation codes on future architectures"
    - "transitive credit as a means to address social and technological concerns stemming from citation and attribution of digital products"
    - "initial findings from a study of best practices and models for cyberinfrastructure software sustainability"
    - "sustainable software development for next gen sequencing ngs bioinformatics on emerging platforms"
    - "experiences with automated build and test for geodynamics simulation codes"
    - "cactus issues for sustainable simulation software"
    - "sustainable software ecosystems for open science"

Connected through hyperedge HE-2 (induced by source paper "first workshop on on sustainable software for science practice and experiences wssspe submission and peer review process and results"):
  with members:
    - "software abstractions and methodologies for hpc simulation codes on future architectures"
    - "initial findings from a study of best practices and models for cyberinfrastructure software sustainability"
    - "sustainable software development for next gen sequencing ngs bioinformatics on emerging platforms"
    - "experiences with automated build and test for geodynamics simulation codes"
    - "cactus issues for sustainable simulation software"
    - "sustainable software ecosystems for open science"
    - "visit experiences with sustainable software"
    - "simplifying the development use and sustainability of hpc software"

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)