Following up on my capstone Project: The Executive Debrief . After the full report, the next challenge was a…
HOROIHEOMA C. — Cybersecurity Analyst
Following up on my capstone Project: The Executive Debrief .
After the full report, the next challenge was a different one: explaining the same project to a board that is short on time,non-technical, and focused on risks and costs. I've attached the executive debrief slides ( https://acrobat.adobe.com/id/urn:aaid:sc:EU:6ea20f2f-68d7-419c-9843-cd39a2e04ea7 ) from my AI in Cybersecurity capstone class project at Brixgate academy.
It takes one flagged login sequence in a fictional fintech and turns it into a story a board can act on immediately: what happened, what it could cost, and what to fix first.
Writing the technical report was one skill. Telling the story in plain words was another. The slides had to explain what matters, why it matters, and what to do next, with no tool names and no jargon.
The lesson from the project still holds. AI can speed up the work, but judgement is still the humans job. Thank you again to Brixgate for a programme that pushed me to think, not just prompt. Feedback is welcome.
#Cybersecurity #AIinCybersecurity #Threatintelligence #IncidentResponse #SOC #GRC #BrixgateAcademy #ContinuousLearning file:///C:/Users/Administrator/Downloads/NimbusPay_Executive_Debrief.pdf
5 reactions · 6 comments
Topics: #continuouslearning, #brixgateacademy, #threatintelligence, #incidentresponse, #aiincybersecurity, #cybersecurity, #soc, #grc
Comments
HOROIHEOMA C.: https://acrobat.adobe.com/id/urn:aaid:sc:EU:6ea20f2f-68d7-419c-9843-cd39a2e04ea7
HOROIHEOMA C.: I'm sorry i have to share the attachment via a link, its dfficult to attach a pdf file to a post on cyberr.ai
HOROIHEOMA C.: Schomer i'm not sure your comment is refering to my post/project.
Schomer: You are completely right, Horoiheoma—my apologies! I had multiple threat-intel tabs open tracking a multi-chain exploit and pasted my analysis onto your thread by mistake. Truly phenomenal work on the NimbusPay debrief, though. Stripping out the technical jargon to tell a clear risk-and-cost story for a non-technical board is a massive skill. Excellent write-up
Schomer: Great work on this, Horoiheoma. Stripping away the tool names and technical jargon to focus strictly on risk, cost, and remediation priorities is exactly what a board needs. Translating a flagged login sequence into an actionable business story is a critical skill that bridges the gap between the SOC and the executive suite