Here is a comprehensive overview of RChilli's Security & Privacy Guide for On-Premises Setup, based on the latest internal documentation:
π RChilli Security & Privacy for On-Premises Deployment
When deploying RChilli products on-premises, maintaining robust security and privacy is central to ensuring compliance and safeguarding sensitive data. RChilli adheres to global standards, integrating security into every phase of product development and deployment.
β Certifications & Compliance
RChilli's infrastructure and software are certified under several major standards, demonstrating a strong commitment to security and compliance:
ISO/IEC 27001:2022 (Valid until Feb 2027)
SOC 2 Type 2 (Valid until December 2026)
PCI DSS and HIPAA (Valid until 2027)
FedRAMP Moderate is in Ready status.
These certifications validate that RChilli enforces industry-standard policies, procedures, and controls to secure data both at rest and in transit.
π§± Security in On-Premises Setup
For on-premise setups, especially those deployed via Docker, RChilli requires specific system configurations to maintain optimal security and performance:
Minimum System Requirements:
64-bit Linux Server (Recommended: CentOS 8/9, Ubuntu, Amazon Linux)
16-Core Processor, 3.x GHz frequency
100 GB RAM or higher
200 GB root volume storage
Docker Environment Setup with API authentication
Reference Guide: Installing RChilli API Using Docker
π Data Security Practices
RChilliβs on-prem API services enforce the following:
REST API Authentication using user keys
Secure API calls with HTTPS
Data isolation per user key
No data storage β parsed resumes are not retained unless explicitly indexed
Even for on-prem deployments, RChilli maintains the same security-first principles as in cloud models.
π Access Control and Network Security
User-based access control: Authentication through secure API tokens (user key, subuser ID)
No internet dependency: Once deployed, all operations (resume parsing, matching, etc.) occur locally
Network segmentation and firewall configurations are recommended to restrict access
π Data Handling Transparency
For on-prem deployments:
No external data transmission is required for parsing or indexing
Customers maintain complete control over data lifecycle
Logs and API usage data remain within the local environment
π‘οΈ Recommendations for Enhanced On-Prem Security
Use internal SSL certificates for Docker environments to secure internal APIs.
Enforce role-based access controls within your local systems managing RChilli services.
Limit network access to the RChilli services to only trusted IPs or systems.
Regularly update Docker containers using RChilli-provided secure base images.
π© Need Help?
For advanced security consultations or assistance with configuring an on-premises setup, contact: Email: support@rchilli.com
Comments
0 comments
Please sign in to leave a comment.