> For the complete documentation index, see [llms.txt](https://amocsub.gitbook.io/blog/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://amocsub.gitbook.io/blog/posts/what-do-we-need-to-know-about-secure-sdlc.md).

# What do we need to know about secure SDLC?

The following is an abstract of all the main topics & tools mentioned at [the meetup](https://www.meetup.com/barcelona-cybersecurity/events/300478646/) made the **9/5/2024.**

{% embed url="<https://docs.google.com/presentation/d/118FajfZZsYGCOpkQR32MksnAwxzURM0kzE2-W8ZQO4A/edit?usp=sharing>" %}
meetup slides
{% endembed %}

### Requirements gathering and analysis

* [OWASP ASVS](https://owasp.org/www-project-application-security-verification-standard/)
* [OWASP SAMM](https://www.bing.com/ck/a?!&\&p=cf608cd6b67ede34JmltdHM9MTcxNTQ3MjAwMCZpZ3VpZD0wYmMxNTU0YS1kMzhhLTYwOTEtMTExYS00MTBlZDI1NzYxNzQmaW5zaWQ9NTIxMQ\&ptn=3\&ver=2\&hsh=3\&fclid=0bc1554a-d38a-6091-111a-410ed2576174\&psq=OWASP+SAMM\&u=a1aHR0cHM6Ly9vd2FzcHNhbW0ub3JnLw\&ntb=1)
* [OWASP Top 10](https://owasp.org/www-project-top-ten/)
* [COBIT](https://www.isaca.org/resources/cobit)
* [NIST SP 800-53](https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final)
* [LOPDGDD](https://www.boe.es/eli/es/lo/2018/12/05/3/con)

### System Design

* [Draw.io Threat Modeling](https://www.drawio.com/blog/threat-modelling) - Recommended
* [Miro](https://miro.com/app/) - General purpose diagramming
* [OWASP Threat Modeling Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/Threat_Modeling_Cheat_Sheet.html)
* [OWASP Threat Dragon](https://owasp.org/www-project-threat-dragon/)

### Coding

For tools mentioned at the talk I think most of them can be or either integrated with an IDE plugin or with pre-commit.

* [Semgrep](https://semgrep.dev/) - Recommended

... to be continued


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://amocsub.gitbook.io/blog/posts/what-do-we-need-to-know-about-secure-sdlc.md?ask=<question>
```

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.