Lost In Space: How to navigate Corporate Security as an Engineer
summary
Corporate security here means securing business functions through stakeholder-driven risk management, not just code. Advice: map stakeholders, track relationships with Notion personal CRM or similar, and log tasks in your issue tracker; build data and software inventory and asset inventories; write runbooks and playbooks and structure docs via information architecture; set meeting agendas with clear deliverables, use async workflows for multi‑timezone teams, and templatize onboarding processes so knowledge survives reorgs and wins become repeatable.
AI-written summary · about
chapters (18)
- 0:00Introduction to corporate security
- 1:47About the speaker’s background
- 2:28Identifying stakeholders in security
- 3:30Building a strong professional brand
- 4:35Effective communication with stakeholders
- 6:20Tracking relationships with stakeholders
- 8:29Documenting work and tracking issues
- 9:12Understanding business through inventories
- 11:20Optimizing collaboration and avoiding duplication
- 12:44Documenting tribal knowledge effectively
- 13:49Information architecture for documentation
- 14:51Choosing the right communication channels
- 16:41Setting clear meeting expectations
- 17:22Using CRM for follow-ups
- 18:04Making allies of stakeholders
- 18:25Handling personnel changes and reorgs
- 19:29Celebrating wins and self-care
- 20:33Q&A session
related talks
25mManaging the Assets of Your Security Career
24mBeing secure by design: Engineer-led security
27mIncluding security in your engineering culture
21mSecuring a Security Company
20mBuilding security culture on infrastructure teams
24mConcrete Steps to Create a Security Culture
19mSo You’re the First Security Hire
36mOvercoming Obstacles in Operationalizing Security