Skip to main content

Platform Features

GoPerfect uses advanced security measures to protect data, control access, and ensure safe integrations.

Viola Di Veroli avatar
Written by Viola Di Veroli
Updated this week

GoPerfect employs a comprehensive suite of security measures designed to protect user data, ensure operational integrity, and maintain compliance with industry standards. Key features include:

  1. Permission Settings and Access Controls:

    • Role-Based Access Control (RBAC): GoPerfect restricts user access based on roles, ensuring that each individual can only view or modify data appropriate to their responsibilities.

    • Audit Trails and Logging: Administrative actions, such as permission changes or data exports, are logged in a tamper-proof system for accountability and to facilitate compliance audits.

  2. Integration Safeguards:

    • Secure API Gateways: Data exchanges with third-party systems, such as CRM and ATS integrations, are secured using industry-standard protocols like OAuth 2.0 for authentication and TLS encryption for data in transit.

    • Data Validation and Monitoring: Incoming and outgoing data is validated to prevent injection attacks or unintentional data corruption. Real-time monitoring ensures immediate alerts if anomalies are detected during integration.

  3. ATS Sync Security:

    • Encrypted Synchronization: All interactions with Applicant Tracking Systems (ATS) utilize advanced encryption standards, such as AES-256, to secure sensitive candidate and job data.

    • Change Management Safeguards: Synchronization events are tracked, with granular logs maintained to trace data movements, minimizing risks of inadvertent data duplication or overwriting.

  4. Continuous Security Enhancements:

    • Proactive Vulnerability Management: Regular penetration testing and vulnerability scanning are conducted to identify and mitigate potential risks before exploitation.

    • Zero-Trust Architecture: Microservices communication within the platform adheres to a zero-trust model, ensuring that only explicitly allowed services can interact, thus minimizing internal exposure.

Need more guidance? πŸ™‹ Our LIVE support team (at the bottom right corner of your screen) replies to ANY question.

Did this answer your question?