CYBOT prioritizes security across authentication, access control, data protection, infrastructure operations, and AI Agent execution. It is designed for organizations that require appropriate controls for security, privacy, and data governance.
This document provides a public-facing overview of CYBOT security measures for customers and users. It avoids internal technical details, production-sensitive information, and information that could affect system security.
1. Authentication and User Management
The system supports multiple authentication approaches, including internal user accounts, identity provider integration, and organization-managed identity systems, so it can align with a customer's existing IT environment.
Passwords are stored using appropriate cryptographic protection, and token-based sessions are used to manage authenticated access securely.
2. Access Control
CYBOT uses Role-Based Access Control (RBAC) to assign access rights based on user roles, such as general users, administrators, or group administrators.
Users can access only the data, features, and modules they are authorized to use. The system validates permissions before allowing access to administrative areas or sensitive information.
3. Data Protection
Data transmitted through the system is protected using encrypted HTTPS/TLS connections to reduce the risk of interception in transit.
Data stored in CYBOT is separated by purpose, such as user information, conversations, events, notifications, and audit-related information. The system is designed to support appropriate access control and traceability.
4. Application Security
CYBOT includes application security controls such as:
- Protection against database command injection
- Validation of incoming data formats
- Request size controls
- Security headers to reduce browser-based risks
- Permission checks for restricted endpoints
These controls help reduce risks such as unauthorized access, injection attacks, clickjacking, and malformed input.
5. Infrastructure Security
CYBOT can be deployed in isolated and controlled environments, such as containerized environments or on-premise servers. Internal services can be designed so they are not directly exposed to external networks.
External access can be routed through a reverse proxy layer responsible for encryption, request handling, and communication security policies.
6. AI Agent Security
CYBOT is designed so AI Agent execution can operate within controlled boundaries, such as limiting file access, limiting processing scope, and separating the agent runtime from the core system.
Where an agent action may affect systems or sensitive data, the workflow can require user confirmation before continuing, keeping human oversight over important decisions.
7. Deployment Options
CYBOT supports deployment options that can align with customer security requirements, such as:
- On-premise deployment
- Deployment in environments with controlled external connectivity
- Deployment with internal AI models to reduce data leaving the customer's environment
8. Continuous Security Improvement
Softnix continuously improves security controls across access review, encryption, secret management, configuration review, and security testing within the development lifecycle.
9. Security Reporting
If customers identify a security concern, they may contact the system administrator or Softnix support team so the issue can be reviewed and handled through the appropriate process.