> ## Documentation Index
> Fetch the complete documentation index at: https://docs.d0pam1ne.blackhatethicalhacking.com/llms.txt
> Use this file to discover all available pages before exploring further.

# State of security deck

> A one-click, editable PowerPoint for the client meeting, built from a project's issues.

The **State of security deck** turns a project into a short presentation you can walk a client through. Download it from the project's **Reports** page (**Download the deck (.pptx)**), or from the **.pptx** button on each client row in **Synapse, Dashboard, By client**.

It is built from the project's issues at that moment, with false positives left out. Every slide is real PowerPoint: native charts, text and shapes you can restyle, reword or extend before the meeting. Slides with nothing to say are skipped.

| Slide | What it shows |
| - | - |
| Cover | Your logo (the project's report branding, else the firm logo from Company identity), the client and project, Prepared for, Prepared by with the firm contact, title, email and phone, the date, and a small Generated by D0pam1ne Pro credit with the D0pam1ne Pro mark |
| At a glance | Open issues, critical or high, overdue against the SLA, and how much is fixed, with a one-line summary and a remediation progress ring (fixed, open, risk accepted) |
| Where the risk sits | Open issues by severity as a chart, split into external and internal when the project has both |
| Where the weaknesses are | The most exposed assets as bars stacked by severity, beside a ring of the types of weakness behind the open issues (shown when there are at least two) |
| Progress over time | Issues found, fixed and still open, week by week (month by month for long engagements), beside a deadline health ring: overdue, due in 30 days, on track. Shown once there are three or more points to plot |
| Top risks to fix first | The most severe open issues with the asset each sits on |
| How an attacker could get in | The strongest [attack path](https://docs.d0pam1ne.blackhatethicalhacking.com/data/attack-surface.md#attack-paths), step by step with why each step leads to the next |
| What has been fixed | The issues closed so far and the share of everything found |
| The next 30 days | What is due or overdue, and how to fix the main weaknesses behind the open issues |
| Next steps | Concrete actions drawn from the numbers: criticals first, overdue items, high issues, breaking the attack path, tracking fixes in the portal |
| Questions | A closing slide with your logo and the firm's contact details, so the meeting ends on your brand |

> [!NOTE]
>
> The attack path slide shows a possible route to prove or rule out, not proof of a compromise, and says so on the slide.

> [!TIP]
>
> The cover uses the same logo as the report: the project's own report branding when one is set, otherwise the firm logo from Settings, Company identity. PowerPoint cannot hold SVG, so an SVG logo is left off the deck; upload a PNG or JPEG logo to have it on the cover.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.