> For the complete documentation index, see [llms.txt](https://docs.mosip.io/1.2.0/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mosip.io/1.2.0/mosip-docs-1.1.5/contribute/coding-standards/security-tools.md).

# Security Tools

| Product Name                  | Description                                                                                                              | Purpose                | Com/Open Source | CI  |
| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------ | ---------------------- | --------------- | --- |
| find\_sec\_bugs               | Scans source code for vulnerable code, Has the abilty to integrate into developer machine. Effective with Java           | SAST                   | Open Source     | Yes |
| [LGTM](https://lgtm.com/)     | A SASS based source code review platform. Its free for open source projects. Can do both Java and javascript             | SAST                   | Free            | Yes |
| OWASP Zap proxy               | This is the best we have and we should use the ZAP and automate all tests                                                | DAST                   | Open Source     | Yes |
| MS Baseline security Analyzer | In case we use a windows infrastructure then this tool is usefull.                                                       | Hardening              | Free            | No  |
| Open Scap                     | We will need to create a custom profile and should be able to scan for hardened OS                                       | Hardening              | Free            | Yes |
| Open Scap                     | Docker scanning                                                                                                          | Docker scan            | Free            | Yes |
| Nessus Vulnerability Scanner  | Vulnerability Scanning                                                                                                   | Vulnerability Scanning | Commercial      | No  |
| Kali linux                    | OS with all the necessary tools to perform a pentest. This would be a lab setup and would be used as part of UAT testing | Penetration Testing    | Open Source     | No  |
| Skipfish                      | Hacking tool set from google.                                                                                            | DAST                   | Open Source     | No  |
| Burp suite                    | A web proxy used for penetration testing of web applications                                                             | DAST                   | Commercial      | No  |

Courtesy : Sasikumar Ganesan


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mosip.io/1.2.0/mosip-docs-1.1.5/contribute/coding-standards/security-tools.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.