July 2020 Summaries

The Developer's Guide to Audit Logs / SIEM provides an in-depth look at audit logs, their importance, event formats, SIEM tools, retention best practices, and more. It explains why audit logs are crucial for app security and how they provide a granular paper trail of user actions within applications. The guide also covers the different types of events to emit, event payloads and formatting, retention windows, building frontends, and integrating with SIEM tools like Splunk and Microsoft's Sentinel. A walkthrough example using Slack is provided to illustrate how successful companies have built great enterprise-ready features through audit logs.

Crossing the Enterprise Chasm is crucial for B2B Cloud SaaS apps to transition from early adopter users to larger enterprise customers. This leap can provide increased product defensibility, decreased customer churn, and expanded market size. However, it's a difficult process due to the complexity of implementing enterprise-ready features such as audit logs, Single Sign On (SSO)/SAML integration, and security policies. It requires significant investment in time and resources, but delaying this transition can result in competitors capturing the lucrative enterprise market segment first. To become enterprise-ready, B2B SaaS apps need to focus on visibility, control, and trust features that meet the requirements of IT administrators.

Slack's incorporation of enterprise features such as SAML SSO, EKM, and audit logs has helped them land big deals with companies like Oracle, IBM, Target, and ETrade. To successfully close enterprise deals, it is crucial to have an enterprise-ready product across the entire company stack. Slack's implementation of authentication features such as SAML/SSO and SCIM, security measures including certifications and EKM, audit logs, RBAC, and strategic communication and pricing has made them a prime example for other companies looking to move up-market.