# NEX Open Source Vulnerabilities ## Description NEX is an open source application which might paves way for any security threat. So, this section helps the user to have some ideas to overcome the issue. ## Mitigation Ideas 1. Maintain a list of "endorsed" deployments (URL list) to capture any unauthorized deployment. 2. Audit all the code including smart contracts, sites regularly. 3. PEN Test run in the production environment related to NEX ## Response Plan 1. Alert message the community about the invaders. 2. Any scope to build API nodes that can blacklist specific services. ## Responder Team In order to find the solution/ to know in details about the risk that has happened, responder team is one to be communicated first. ### First Responder Team If any suspicious activities are observed, the observer can inform about it through any User forum. All the users must be informed about it. ### Second Responder Team **Point of contact:** DEV OPS, NEX devs --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://community.peerplays.com/risk-register/introduction/credential-security/nex-open-source-vulnerabilities.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.