> For the complete documentation index, see [llms.txt](https://playbooks.equalexperts.com/secure-delivery-playbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://playbooks.equalexperts.com/secure-delivery-playbook/practices/organise/intelligence.md). # Intelligence ## Make security visible in the software catalogue The organisation should provide a central view of all software products they create, including relevant metadata (e.g. owning team, deployed versions, links to operability dashboards, source repo, build jobs, etc.). This should be automatically kept up to date, preferably by pulling the information directly from the relevant systems (e.g. GitHub, Jenkins, Grafana, Kibana, deployment tooling, etc.). Security Engineering should ensure that security tooling is integrated with the software catalogue or inventory so that teams can be easily informed of the security issues in their services and understand the issues they are accountable for. This also provides a high-level view of where the greatest risk is and which projects need more assistance from Security Engineering. ## Conduct a post-mortem after security incidents Security Engineering should ensure that blameless post-mortems are conducted after every security incident, involving representatives across the organisation. A post-mortem is a written record of an incident, its impact, the actions taken to mitigate or resolve it, the root cause(s), and the follow-up actions to prevent the incident from recurring. The post-mortem should be shared within the organisation so that other teams can learn valuable lessons and to encourage a culture of openness and disclosure. Examples of other companies that have done this publicly: * [Gentoo GitHub admin compromise](https://wiki.gentoo.org/wiki/Project:Infrastructure/Incident_Reports/2018-06-28_Github) * [GitHub DDoS attack](https://github.blog/2018-03-01-ddos-incident-report/) * [Homebrew GitHub personal access token leak](https://brew.sh/2018/08/05/security-incident-disclosure/) * [Parity hacked via security bug introduced during refactoring](https://www.parity.io/the-multi-sig-hack-a-postmortem/) * [Insider bitcoin theft from ShapeShift](http://moneyandstate.com/looting-of-the-fox/) --- # 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, and the optional `goal` query parameter: ``` GET https://playbooks.equalexperts.com/secure-delivery-playbook/practices/organise/intelligence.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.