Security
Knoledgr Security Annex
This annex summarizes the technical and organizational safeguards Knoledgr uses to support tenant isolation, secure delivery, operational resilience, and enterprise assurance across the platform.
Program, access, and transport protection
- Knoledgr maintains a security program intended to support product reliability, organization isolation, controlled operations, and incident readiness.
- Administrative and production access is intended to follow role-based and least-privilege principles, with privileged actions limited to authorized personnel.
- The platform is designed to use TLS or equivalent protections for data transmitted over public networks, while sensitive credentials and tokens are expected to be handled through restricted operational workflows.
Isolation, delivery, and remediation
- Organization-scoped product and backend workflows are designed to keep customer records and operational reads isolated except for intentionally restricted platform-administration functions.
- Application and infrastructure changes are expected to move through controlled development and deployment workflows rather than unmanaged direct changes.
- Security issues are reviewed through remediation workflows that account for severity, exposure, exploitability, and customer impact.
Monitoring, incident response, and resilience
- Audit logging, monitoring, and alerting are used to support troubleshooting, access review, abuse investigation, and security-relevant detection where operationally appropriate.
- Incident response procedures are intended to support triage, containment, remediation, recovery, and customer communication when a confirmed incident affects customer data.
- Continuity and recovery approaches depend on the service component, hosting configuration, customer plan, and any negotiated enterprise commitments.
Vendor oversight and shared responsibility
- Third-party providers may support infrastructure, communications, monitoring, billing, storage, and AI or model functionality and are managed according to contractual and operational expectations appropriate to the service provided.
- Customers remain responsible for what data they place into the service, how they configure roles and integrations, and how their personnel use the platform.
- Enterprise security and assurance requests can be sent to the Knoledgr security team.