Snapshot 223962
Normalized text
Scripts and page chrome removed; this is what change detection compares.
Enterprise security Security at base14 At base14, security is not an afterthought, a compliance checkbox, or a layer we apply at the end. It is a foundational design principle that shapes how we build, operate, and evolve our observability platform. Compliance Compliance and certifications base14 meets the security requirements of regulated industries including financial services, healthcare, and enterprise SaaS. ISO 27001 Certified Information Security Management System SOC 2 Type II Service Organization Controls Philosophy Security by design Security by design From day one, our architecture has been shaped around security as a core tenet. Every system component—storage, network boundaries, ingestion pipelines, and internal services—is designed with least-privilege access, strict isolation, and auditable data flows. We treat secure-by-default as the only acceptable baseline. Features and infrastructure decisions are evaluated not only for performance and reliability, but for their security posture and long-term trust implications. Enterprise regulatory-grade experience base14 is founded and built by engineers with deep experience delivering software in highly regulated industries such as financial services and healthcare. We have designed and operated platforms that undergo continuous third-party audits, penetration testing, and global compliance reviews. The same discipline and scrutiny guide our work here—ensuring that the systems we build are not just secure in theory, but resilient in real-world, adversarial environments. Controls Hardened access controls Hardened access controls All access to our internal systems requires strong authentication, enforced through mandatory multi-factor authentication (MFA/2FA). Administrative operations follow strict approval workflows, and system access is continuously monitored, logged, and audited. All communication between services—internal or external—uses encrypted channels (TLS 1.3), with automated certificate management and rotation. We maintain a principle of zero direct access to production data, and any temporary access is time-bound and fully audited. Secure engineering culture Security extends beyond infrastructure. Every base14 engineer and operational staff member undergoes regular information security and privacy training. All company-managed devices use full-disk encryption, endpoint protection, and continuous threat monitoring. Security practices are embedded in our development lifecycle—from code reviews and dependency scanning to continuous integration checks and incident response drills. Overview Security features summary A concise overview of the core security guarantees provided by base14 across infrastructure, operations, and culture. Architecture Secure-by-Design Security built into core design; isolation and least-privilege at every layer. Encrypted Data in Transit All communication secured using TLS 1.3 with automated certificate rotation. Segmented Tenant Isolation Each tenant's data is processed and stored in isolation, ensuring strict data boundaries. No Direct Production Access Access to production data is disabled by default; temporary access is time-bound and audited. Access Controls Mandatory MFA/2FA All internal access requires strong multi-factor authentication. Role-Based Permissions Strict IAM policies limiting access to the minimum required scope. Continuous Session Monitoring All privileges and activities are logged and monitored for anomalies. Operational Security Hardened Employee Devices Full-disk encryption, endpoint protection, and continuous threat detection are enforced. Security Training All engineers and staff undergo recurring infosec and privacy training. Controlled Admin Operations All administrative or configuration changes follow documented approval workflows. Data Handling Log/Trace/Metric Protection All telemetry handled through controlled ingestion pipelines with configurable retention. Restricted Data Visibility Internal users only see anonymized or scoped-down data for debugging. Development Practices Secure SDLC Code reviews, automated dependency scanning, and CI security checks. Regular Penetration Testing Independent penetration testing at least annually by certified professionals. Vulnerability Management Continuous monitoring and patching of dependencies and infrastructure. Organizational Trust Experienced Leadership Founders with backgrounds in fintech and healthcare compliance. Incident Response Readiness Documented, tested response plans for security events. Transparent Communication Clear and timely communication in the rare event of a customer-impacting issue. Commitment Our commitment Our customers trust us with sensitive operational telemetry—and we take that responsibility seriously. As we grow, security continues to guide our decisions, our culture, and the evolution of our platform. We will always prioritize the safety of your data over convenience or speed, and we remain committed to maintaining the highest standards of security across every facet of base14. Report a vulnerability Email legal@base14.io. Good-faith research that follows the Safe Harbor Conditions in Section 4.2 of our Terms of Service will not be pursued. We acknowledge reports within five business days. Questions about our security? We're happy to discuss our security practices and how we protect your data Email legal@base14.io