Skip to main content

Katonic MLOps Platform Security

Enterprise-Grade Security has implemented comprehensive security controls across every aspect of product development, hosting, and delivery life cycles. These security controls were developed and implemented with the singular goal of safeguarding our customer’s data using best-in-class industry frameworks and practices. Katonic MLOps platform security includes consideration of data encryption, transfer, communication, and backups for data and code protection, as well as access control within the platform to maintain distinct access to projects and workloads according to permissions.

Security data and access

Data Encryption at Rest and in Transit

Data is encrypted any time it is "at rest" in the Katonic platform, including in "blob store", and on-disk on the "executor" machines that run user scripts. Data is encrypted during transit between users’ machines and different parts of the Katonic platform. Industry-standard TLS for encrypted communication is used.

Authentication and Access Controls

Katonic seamlessly integrates with your identity infrastructure. Users can authenticate against your existing identity provider over LDAP or take advantage of single sign-on using SAMLv2.0 or OIDC-based protocols. For customers that use single-sign-on (SSO), Katonic provides the ability to centrally manage Katonic organizational membership and Katonic system role assignment based on login attributes generated by your identity infrastructure.

For organizations that do not leverage identity federation, Katonic provides a robust built-in identity a manager that offers enterprise-grade functionality like two-factor authentication, password complexity and expiration policies, and secure credential recovery.

Within Katonic, access can be controlled at multiple levels (system, project, and application) by assigning roles that confer a set of permissions to users and groups.


Katonic extensively logs actions in the platform, including access and security-related actions. Logs can be made available to administrators for auditing.

Security for Cloud and VPC deployments

Infrastructure Overview

The Katonic physical infrastructure is hosted and managed by cloud infrastructure providers (AWS, GCP, Azure). The cloud provider manages physical security risk and undergoes recurring assessments to ensure compliance with industry standards. The Katonic installation is deployed in a private cloud instance which can be accessed over VPN, limited to a corporate network, so it is not internet accessible.

Network Access Security

All-access is denied by default, and only explicitly allowed ports and protocols are accessible based on business needs. Each system is assigned to a firewall security group based on its function. With respect to AWS, Security groups associated with the EC2 instance restrict access to only the ports and protocols required for the system-specific function in order to mitigate risk. Similarly, Google Cloud Platform offers firewall rules to secure Compute Engine virtual machine instances and networks. In Azure, the network security group contains security rules that allow or deny inbound traffic or outbound traffic to Azure resources.

User Files

The contents of project files reside on encrypted S3 buckets (AWS) or the equivalent as implemented by the cloud infrastructure provider.

Code Execution

Scripts that run on the Katonic platform run within their own isolated environment. This restrictive operating environment is designed to enhance security (of users’ code and data files) and prevent stability problems. These self-contained environments isolate processes, memory, and the file system using Docker security best practices while host-based firewalls restrict applications from establishing local network connections.

Data Preservation and Backup

Katonic data and configurable, periodic backups reside on encrypted storage, as implemented by the infrastructure provider.

System Authentication

Operating system access can be provisioned for support purposes, and requires username and key authentication. Operating systems do not allow password authentication to prevent password brute force attacks, theft, and sharing.

Employee Security Policies and Procedures

Trusted by financial institutions, pharmaceutical companies, and government entities, Katonic sets the highest standards for security policies, employee culture, and internal security.

System Access for Katonic Employees

Katonic follows a principle of least access. Access is only granted as needed for the job function. Two-factor authentication is required for all systems that support Katonicsoftware and systems (e.g. Google Apps, Github). Complex password requirements are enforced for all capable systems. For Katonic’s cloud platform, administrative work is performed via a bastion host also requiring two-factor authentication.

Logging Security

Logging Capabilities are enabled with best practices applied. Katonic has walked through incident reconstruction in collaboration with the AWS Focus team.


Reference checks are performed for all prospective employees, with all employees and contractors required to sign non-disclosure agreements.

Security Awareness Training:

All employees undergo security training before accessing any customer data. All technical employees also receive a security newsletter every week. The employees are trained on and are made aware of email scams, hoaxes, malware detection, phishing attacks, social networking dangers, safe internet habits, clean desk practice, and how to handle and secure sensitive data.

Access to Customer Data

Katonic staff does not access or interact with customer data or applications as part of normal operations, and does not access a cloud-hosted or on-premises deployment without specific permission. Katonic does not remove customer data from the cloud platform. Cases may exist where Katonic is requested, by the customer, to interact with customer data or applications for support purposes or where required by law.

Developing Secure Software at Katonic

Software Development Lifecycle (SDLC)

Security is incorporated into the SDLC at multiple points. During the design and planning for new features, security implications are an explicit facet of analysis. Security functionality is extensively tested.

Policy Compliance

The Katonic infosec team is responsible for monitoring and enforcing policy compliance using various methods, including but not limited to: periodic walk-throughs, business tool reports, and internal and external audits. Any exceptions to following security policies must be approved in advance. Employees who violate security-related policies are subject to disciplinary action and possible termination.

Source Code Policies’s source code is stored in a central repository where both current and past versions of the service are auditable. The infrastructure is configured to require that a service’s binaries be built from specific reviewed, checked in, and tested source code. Code reviews require inspection and approval from at least one engineer other than the author, and the system enforces that code modifications to any system must be approved by the owners of that system. These requirements limit the ability of an insider or adversary to make malicious modifications to source code and also provide a forensic trail from the service back to its source.

Static Code Analysis

Static code analysis tools are in place to ensure that secure programming guidelines are adhered to and violations get flagged and alerted.

Continuous Integration and Deployment

Continuous integration and deployment pipelines have been built to execute comprehensive quality checks on every code modification and successful test execution is required before deployment to production.