Security & Privacy in Digital First Businesses (Panel)
summary
Front-end teams often ship insecure code until CI blocks it; one group builds Sentinel and gatekeeper as CI gates that run dependency scans and fail the build on alerts. Automation reduces drift but requires human decisions about what to test, especially UX flows like forgot‑password. PCI breaches cost months to remediate and reputation loss; OWASP guidance and conformance test suites are used to prioritize fixes. The panel favors baking security into tests early and continuous auditing rather than one‑time certification.
AI-written summary · about
chapters (6)
- 0:00Start
- 1:12The Need for More Explicit Education and Training Paths for Our Teams
- 8:35Password Restriction
- 10:23Standards and Test Suites
- 28:47How Much Transparency or Information Do You Think Is Owed to Consumers about the Way in Which Their Data Is To Be Used
- 41:24Challenges
related talks
49mPragmatic Approaches To Building Secure Software
49mPanel: From Code to Defense: Why Developers Are the New Security Leaders
27mSecurity: The Thing That Everyone...
26mBeyond Testing: Application Security in the Age of DevOps
52mContinuous Security
44mApplication Security: Everything we know is wrong
38mPrioritizing Trust While Creating Applications
40mDesign Approaches for Security Automation