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: "a comprehensive formal security analysis of oauth 2 0"
  Abstract: The OAuth 2.0 protocol is one of the most widely deployed authorization/single sign-on (SSO) protocols and also serves as the foundation for the new SSO standard OpenID Connect. Despite the popularity of OAuth, so far analysis efforts were mostly targeted at finding bugs in specific implementations and were based on formal models which abstract from many web features or did not provide a formal treatment at all. #R##N#In this paper, we carry out the first extensive formal analysis of the OAuth 2.0 standard in an expressive web model. Our analysis aims at establishing strong authorization, authentication, and session integrity guarantees, for which we provide formal definitions. In our formal analysis, all four OAuth grant types (authorization code grant, implicit grant, resource owner password credentials grant, and the client credentials grant) are covered. They may even run simultaneously in the same and different relying parties and identity providers, where malicious relying parties, identity providers, and browsers are considered as well. Our modeling and analysis of the OAuth 2.0 standard assumes that security recommendations and best practices are followed, in order to avoid obvious and known attacks. #R##N#When proving the security of OAuth in our model, we discovered four attacks which break the security of OAuth. The vulnerabilities can be exploited in practice and are present also in OpenID Connect. #R##N#We propose fixes for the identified vulnerabilities, and then, for the first time, actually prove the security of OAuth in an expressive web model. In particular, we show that the fixed version of OAuth (with security recommendations and best practices in place) provides the authorization, authentication, and session integrity properties we specify.

Connected through hyperedge HE-1 (induced by source paper "language based web session integrity"):
  with members:
    - "the web sso standard openid connect in depth formal security analysis and security guidelines"

Connected through hyperedge HE-2 (induced by source paper "oauthguard protecting user security and privacy with oauth 2 0 and openid connect"):
  with members:
    - "wpse fortifying web protocols via browser side security monitoring"
    - "the web sso standard openid connect in depth formal security analysis and security guidelines"
    - "analysing the security of google s implementation of openid connect"

Connected through hyperedge HE-3 (induced by source paper "an extensive formal security analysis of the openid financial grade api"):
  with members:
    - "the web sso standard openid connect in depth formal security analysis and security guidelines"
    - "analysing the security of google s implementation of openid connect"
    - "analyzing the browserid sso system with primary identity providers using an expressive model of the web"

Connected through hyperedge HE-4 (induced by source paper "verifying security protocols using dynamic strategies"):
  with members:
    - "atpboost learning premise selection in binary setting with atp feedback"
    - "formal analysis of 5g authentication"
    - "automated proof synthesis for propositional logic with deep neural networks"
    - "holstep a machine learning dataset for higher order logic theorem proving"
    - "deepmath deep sequence models for premise selection"
    - "end to end memory networks"
    - "a hybrid analysis for security protocols with state"

Connected through hyperedge HE-5 (induced by source paper "the web sso standard openid connect in depth formal security analysis and security guidelines"):
  with members:
    - "analysing the security of google s implementation of openid connect"
    - "analyzing the browserid sso system with primary identity providers using an expressive model of the web"

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)