Security Behind the Curtains With Event Monitoring
summary
Backstage Auditor v1.36 is a built‑in service that captures API accesses, config changes and outcomes with a simple API: createEvent / success / fail and stores actor info, URL and method only to keep logs small. Events carry severity low, medium, high, critical, route to configurable Winston streams or external systems like Splunk or Elasticsearch, and support metadata for forensic analysis. BEP review takes ~2 months, implementation ~4 months, and three plugins already adopt it (scaffolder, catalog, rbac) while session tracking is still pending.
AI-written summary · about
chapters (10)
- 0:00Backstage security needs
- 1:02Dedicated auditing essential
- 2:06Introducing Backstage Auditor
- 4:15How Auditor API works
- 7:29Live demo Auditor implementation
- 16:03Customizing Auditor output
- 18:31Key benefits Auditor service
- 19:36Auditor development journey
- 21:41Future Auditor enhancements
- 22:46Key takeaways and impact
related talks
23mUsing CD Events to Capture End to End Application Security Posture
51mScale Your Auditing Events
19mCentralized Compliance: Automated Governance Inside of Backstage...
49mScale Your Auditing Events
41mWhat the Log?! So Many Events, so Little Time...
51mSecurity incident monitoring, mitigation & metrics using feature flags
23mSecuring Your Software Delivery Chain with Process Auditing
26mAuditing Laravel