Kolidiscope, Inc. is committed to building and operating secure products. This page outlines the software development lifecycle, infrastructure security, and open source component management practices used across our products, including the Pareskope platform.
Kolidiscope, Inc. follows a structured SDLC to ensure code quality, reliability, and security across all releases.
All source code is managed in private Git repositories with branch protection policies. Direct commits to production branches are prohibited.
All changes require peer review and approval before merging. Reviews evaluate correctness, security implications, and adherence to coding standards.
Continuous integration pipelines run unit tests, integration tests, and static analysis on every commit. Builds must pass all checks before deployment.
Changes are deployed to a staging environment for validation before production release. Production deployments follow a controlled release process.
Applications are packaged and deployed using Docker containers, ensuring consistent runtime environments and reproducible builds across all stages.
Production systems are continuously monitored for performance, errors, and anomalies. Alerts trigger defined incident response procedures.
All data is encrypted in transit using TLS 1.2 or higher. Data at rest is encrypted using AES-256. Encryption keys are managed through cloud-native key management services.
The Pareskope platform is hosted on SOC 2-compliant cloud infrastructure with automated backups, redundancy, and disaster recovery capabilities. Infrastructure is provisioned and managed using infrastructure-as-code practices.
Platform access is governed by role-based access controls (RBAC). Administrative access requires multi-factor authentication. All access events are logged and auditable.
Customer environments are logically isolated. Data is segregated at the application and storage layers. No customer data is shared across tenants or accessible to other customers.
Kolidiscope, Inc. maintains a disciplined approach to incorporating and managing open source software.
We maintain a complete software bill of materials (SBOM) listing all open source components, versions, and licenses incorporated into the platform.
All open source components are evaluated for license compatibility before adoption. We use only components with permissive licenses (BSD, MIT, Apache 2.0, PSF).
Dependencies are regularly scanned for known security vulnerabilities. Critical and high-severity findings are remediated on a prioritized timeline.
Dependencies are pinned to specific versions. Updates are tested in staging before promotion. We track upstream releases and security advisories for all components.
Our complete software bill of materials is publicly available at /opensource, including all component names, license types, SPDX identifiers, and links to source licenses.
Kolidiscope, Inc. maintains a current and complete SBOM that documents every open source component incorporated into the Pareskope platform. The SBOM includes component names, versions, license types, and SPDX license identifiers.
The full SBOM is available on our Open Source Attributions page and is updated whenever components are added, removed, or upgraded.
Customer data is processed solely for the purpose of delivering contracted services. We maintain strict data retention policies — customer data is retained for the duration of the service agreement and securely deleted upon termination in accordance with agreed-upon timelines.
Customer data is never used for model training, benchmarking, or any purpose beyond direct service delivery without explicit written authorization.
For security inquiries, to request detailed documentation, or to discuss specific compliance requirements, contact us at .