Kentik

Security isn't a single yes/no, but Kentik is SOC 2 Type II compliant and holds SOC 2 Type II, GDPR. SOC2C verifies its compliance posture and shows how strongly each fact is proven.

Kentik hasn't listed a bug bounty or vulnerability disclosure program on SOC2C. Many companies accept security reports at security@kentik.com or via a /security page (Kentik lists a security contact).

Kentik lists 10 subprocessors on its trust center, including Amazon Web Services, Google Cloud Platform, Microsoft Azure, Oracle (OCI), PagerDuty. Buyers use this for fourth-party risk review.

Kentik hosts on AWS, GCP, Azure, and handles Credit card information, Personal health information, IP addresses, Network metadata. Data residency details are on its trust center.

Kentik's trust center is at https://trust.kentik.com. Its verified SOC 2 status, frameworks, and documents are summarized on its SOC2C profile.

For a high level overview of our security program, please see our Security Whitepaper available in the sidebar of this Trust Center or at: https://www.kentik.com/pdfs/KentikSecurityOverview.pdf. For a detailed technical overview, please see our Knowledge Base (KB) article and Q&A at: https://kb.kentik.com/v0/Ab03.htm#Ab03-Security_Overview If you'd like to speak with a member of our security team, please reach out via your Sales or Customer Success contact to get connected.

We have a dedicated Chief Security Officer (CSO) who reports directly to the CEO and communicates regularly with our Board of Directors. In addition, we dedicated roles, such as Security Assurance Management staff responsible for privacy & compliance, as well as technically-focused security resource(s) including a Staff Security Engineer. Our Security staff work collaboratively with members from other departments, including member of Engineering, Infrastructure, HR, Legal, Sales, and CSM teams.

Kentik Technologies, Inc 548 Market St PMB 78595, San Francisco, CA 94104-5401

Yes - our status page is publicly-accessible at https://status.kentik.com/ (US) and https://status.kentik.eu/ (EU), which includes a variety of subscription options.

We publish release notes to https://new.kentik.com/ for our system updates, which are also made available to platform users in-app. This page includes support for email, slack, and RSS-based subscriptions. You can also find our release testing application at https://next.kentik.com/login to review upcoming features.

Yes, we have a DPA that includes the EU Standard Contractual Clauses (EU SCCs) that describes our commitments for safeguarding the processing of EU resident data. Please visit https://www.kentik.com/pdfs/KentikDataProtectionAddendum.pdf for the most recent version.

Yes, please see https://www.kentik.com/pdfs/KentikSupportSLA.pdf for our most recent copy for our standard SaaS service. Please note that customer-specific agreements may supersede standard terms.

Yes - all data is encrypted at rest using AES-256 or better. We use self-encrypting hard drives that support OPAL 2.0 commands, so encryption keys are never directly accessible to our staff.

Yes - all Kentik-controlled data is encrypted in transit across public networks using TLS 1.2 or better (TLS 1.3 is supported). This includes access to our SaaS platform, API, and similar resources. The Kentik Platform ingests information from our customers, including netflow, SNMP, streaming telemetry, and similar data sent to our systems. We make sure to provide multiple mechanisms for customers to encrypt data in route to us; however, encryption of this information *does* require a small amount of customer configuration. If you need help with this, our Sales Engineers and Customer Success staff are happy to assist. To make this easy, we provide customers with an agent that can collect, aggregate, & encrypt data sent to us. For more information, please see https://kb.kentik.com/v0/Ab08.htm#Ab08-Encryption\_AgentEncryption\_Agent. We also support options for private network interconnects (PNIs) directly to our server infrastructure.

We support MFA for all logins, with support for app-based authenticators (such as Google Authenticator) and hardware security tokens, including Yubikeys. We also support & recommend the use of SSO integrations via SAML 2.0. To dive into our SSO details, please see our KB page. !image/list of confirmed SSO integrations

For more information, please review our security whitepaper at https://www.kentik.com/pdfs/KentikSecurityOverview.pdf. In short, our SDLC includes the following major commitments: - All code is tested using both manual and automated tests, with at least one individual other than the author signing off on the change. - All changes are tracked in project management, code repository, and CI/CD systems to ensure changes are recorded, validated, and can be reverted in the event of unexpected behavior. - All code is subject to peer review. - All code is evaluated using a static code analysis system to identify potential security mistakes or use of insecure libraries & dependencies. - Code is tested in non-production environments before migration to production. - Raw production data is never used in non-Production environments. - Maintenance windows and performance issues are documented on dedicated status pages (US: https://status.kentik.com/, EU: https://status.kentik.eu/). - Developers are trained on secure software development practices and corporate security requirements. - Infrastructure is managed using configuration management systems to reduce the chances for human error or configuration drift

Software vulnerabilities are evaluated in real time within our CI/CD tooling. We perform weekly vulnerability scans against our infrastructure using a well-respected platform to check for known security flaws. Any issues are tracked by Security staff and subject to remediation according to defined SLAs.