Founded in 2017
Haber recognises that the confidentiality, integrity and availability of information and data created, maintained and hosted by us are vital to the success of the business and privacy of our partners.
As a service provider/product, we understand the importance in providing clear information about our security practices, tools, resources and responsibilities within Haber so that our customers can feel confident in choosing us as a trusted provider.
This Security Posture highlights high-level details about our steps to identify and mitigate risks, implement best practices, and continuously develop ways to improve.
Founded in 2017
|
|
Controls (86)
Here are the controls implemented at Elixa Technologies Pvt Ltd to ensure compliance, as a part of our security program.
Product security (8)
Production System User Review
Entity's Infosec officer reviews and approves the list of people with access to production console annually
Situational Awareness For Incidents
Entity maintains a record of information security incidents, its investigation, and the response plan that was executed in accordance with the policy and procedure defined to report and manage incidents.
Vulnerability Remediation Process
Entity identifies vulnerabilities on the Company platform through the execution of regular vulnerability scans.
Centralized Management of Flaw Remediation Processes
Entity tracks all vulnerabilities and remediates them as per the policy and procedure defined to manage vulnerabilities.
Product Architecture
Haber is a cloud-based platform hosted entirely on Amazon Web Services (AWS), built for scalability, isolation, and resilience. The platform runs inside a Virtual Private Cloud (VPC) that provides a secure, logically isolated network environment for application services, databases, and supporting systems. All customer data is encrypted in transit using TLS 1.2 or higher and at rest using AES-256. Access to production infrastructure is governed by the principle of least privilege through identity and access management policies, and all activity is logged for accountability and monitoring. The architecture leverages cloud-native security services for web-application firewalling, threat detection, DDoS protection, and continuous monitoring of infrastructure and application health.
Environment Segregation
Haber maintains separate, isolated environments for development, staging, and production. Only the production environment has access to production data; development and staging environments use non-production data. Developers do not have direct access to the underlying production infrastructure, and production systems are managed through controlled tooling and monitored access paths. This separation reduces deployment risk and prevents unauthorized exposure of customer data during development and testing.
Change Management Program
Haber operates a documented change management process governing changes to application code, infrastructure, and configuration. Proposed changes are assessed for business, security, and stability impact, developed and tested in non-production environments, and require review and approval before deployment to production. A quality-assurance process validates stability prior to release, and all changes including emergency changes are documented and tracked through a centralized ticketing system to maintain traceability and accountability.
Session Termination
Application sessions are subject to an idle session timeout, after which users must re-authenticate. Session controls help protect against unauthorized access from unattended sessions across web and administrative interfaces.
Data security (17)
Identity Validation
Entity ensures that logical access provisioning to critical systems requires approval from authorized personnel on an individual need or for a predefined role.
Termination of Employment
Entity ensures logical access that is no longer required in the event of termination is made inaccessible in a timely manner.
Production Databases Access Restriction
Entity ensures that access to the production databases is restricted to only those individuals who require such access to perform their job functions.
Multi-factor Authentication
Entity requires that all staff members with access to any critical system be protected with a secure login mechanism such as Multifactor-authentication.
User Privileges Reviews
Entity's Senior Management or the Information Security Officer periodically reviews and ensures that access to the critical systems is restricted to only those individuals who require such access to perform their job functions.
User Access Reviews
Entity's Senior Management or the Information Security Officer periodically reviews and ensures that administrative access to the critical systems is restricted to only those individuals who require such access to perform their job functions.
Encrypting Data At Rest
Entity has set up cryptographic mechanisms to encrypt all production database[s] that store customer data at rest.
Inventory of Infrastructure Assets
Entity develops, documents, and maintains an inventory of organizational infrastructure systems, including all necessary information to achieve accountability.
Data Backups
Entity backs up relevant user and system data regularly to meet recovery time and recovery point objectives and verifies the integrity of these backups.
Testing for Reliability and Integrity
Entity tests backup information periodically to verify media reliability and information integrity.
Data Retention
Haber maintains a documented data retention policy aligned with applicable legal, regulatory, and contractual requirements. Active customer data is retained for the duration of the contract. Following termination, data is retained for a defined contractual grace period to allow for export or return, after which it is securely deleted in accordance with our retention schedule.
Data Deletion & Erasure
Upon contract termination and expiry of the agreed retention period, customer data is securely and permanently deleted from Haber's systems in line with contractual terms. Decommissioning of storage media at the cloud-infrastructure layer follows recognized media-sanitization standards.
Data Classification
Haber classifies information assets according to sensitivity (for example: Public, Internal, Confidential, and Restricted) and applies handling, access, and protection requirements appropriate to each level. All data received from customers, including any personal data, is treated as Confidential and protected with corresponding security controls.
Audit Logging
Haber maintains audit logs across its systems capturing "who, what, where, and when" detail for system access and changes. Logs include administrator and user actions and record the source of each event. Logs are retained in accordance with our logging policy, protected from tampering, and monitored to support security investigations and accountability.
Password Policy
Haber enforces a password policy for internal systems requiring a minimum length, complexity (a mix of character types), account lockout after repeated failed attempts, and periodic rotation. Reuse of previous passwords is prohibited, and credentials must be distinct from the user ID. Where supported, access is further protected by multi-factor authentication.
Secret & Credential Management
Application secrets, credentials, and encryption keys are stored in a dedicated, access-controlled secrets-management system and a managed key-management service rather than in source code or configuration files. Secrets are access-restricted on a least-privilege basis and rotated periodically to limit the impact of any potential exposure. Static analysis is used to help detect and prevent secrets from being committed to code repositories.
Physical Security
Haber's platform and customer data are hosted in AWS data centers, which enforce industry-standard physical security controls including 24/7 on-site security, multi-factor entry controls, CCTV surveillance, and strict access logging. Haber's own offices apply physical security measures such as access-controlled entry, visitor registration, and surveillance. Haber does not operate its own server rooms; all production data is hosted in the cloud.
Network security (11)
Impact analysis
Entity systems generate information that is reviewed and evaluated to determine impacts on the functioning of internal controls.
Limit Network Connections
Entity ensures that the production databases access and Secure Shell access to infrastructure entities are protected from public internet access.
External System Connections
Every Production host is protected by a firewall with a deny-by-default rule. Deny by default rule set is a default on the Entity's cloud provider.
Transmission Confidentiality
Entity has set up processes to utilize standard encryption methods, including HTTPS with the TLS algorithm, to keep transmitted data confidential.
Anomalous Behavior
Entity's infrastructure is configured to review and analyze audit events to detect anomalous or suspicious activity and threats
Capacity & Performance Management
Entity has set up methods to continuously monitor critical assets to generate capacity alerts to ensure optimal performance, meet future capacity requirements, and protect against denial-of-service attacks.
Data used in Testing
Entity ensures that customer data used in non-Production environments requires the same level of protection as the production environment.
Centralized Collection of Security Event Logs
Entity's infrastructure is configured to generate audit events for actions of interest related to security for all critical systems.
Network Penetration Testing
Haber engages independent third parties to perform external vulnerability assessment and penetration testing (VAPT) of its network, applications, and APIs at least annually and after significant changes. Testing covers the OWASP Top 10 and other relevant vulnerability classes. Findings are risk-rated, tracked, and remediated according to defined timelines. Automated vulnerability scans are additionally run on at least a monthly basis.
Web Application Firewall
A web application firewall (WAF) is deployed at the edge of Haber's infrastructure to inspect inbound traffic and protect web applications against common attacks such as SQL injection, cross-site scripting (XSS), and other OWASP-class exploits.
Remote Access
Administrative access to production infrastructure is restricted to authorized personnel and is performed only over encrypted channels (such as SSH over a VPN or bastion entry point) with multi-factor authentication. Access is governed by role-based controls, and all sessions are logged and monitored.
App security (9)
Conspicuous Link To Privacy Notice
Entity displays the most current information about its services on its website, which is accessible to its customers.
Secure system modification
Entity has procedures to govern changes to its operating environment.
Approval of Changes
Entity has established procedures for approval when implementing changes to the operating environment.
Unauthorized Activities
Entity uses Sprinto, a continuous monitoring system, to alert the security team to update the access levels of team members whose roles have changed.
Application Penetration Testing
Haber's web products and API surfaces undergo independent third-party penetration testing at least annually and following major changes. Assessments cover the OWASP Top 10 and other applicable security risks. Identified issues are prioritized by severity, tracked to closure, and re-tested to confirm remediation.
Secure Software Development Lifecycle
Haber follows a documented secure development lifecycle (SDLC) incorporating secure-coding and quality-assurance practices aligned with SOC 2 requirements and guidance from sources such as OWASP, NIST, and SANS. Security and privacy considerations are built in by design, and a dedicated QA function is responsible for change quality and platform stability prior to release.
Code Analysis
Haber uses static application security testing (SAST) to automatically scan code including third-party dependencies for vulnerabilities and licensing issues before it is promoted to production. Scans run as part of the deployment pipeline, and identified issues are remediated according to severity.
Vulnerability & Patch Management
Haber maintains a documented vulnerability and patch management process. Code and dependencies are continuously scanned for vulnerabilities, and infrastructure is scanned at least monthly. Operating-system and security patches are tested for stability in staging before being prioritized and deployed to production, with critical and security patches expedited under defined timelines.
Secure Development Training
Developers receive training on secure coding and secure-by-design practices covering areas such as authentication, authorization, session management, input validation, and secure communications, drawing on industry guidance (OWASP, NIST, SANS). All personnel with access to customer data also complete data-security and privacy training.
Endpoint security (6)
Malicious Code Protection (Anti-Malware)
Where applicable, Entity ensures that endpoints with access to critical servers or data must be protected by malware-protection software.
Full Device or Container-based Encryption
Where applicable, Entity ensures that endpoints with access to critical servers or data must be encrypted to protect from unauthorized access.
Endpoint Security Validation
Entity has set up measures to perform security and privacy compliance checks on the software versions and patches of remote devices prior to the establishment of the internal connection.
Session Lock
Entity ensures that endpoints with access to critical servers or data are configured to auto-screen-lock after 15 minutes of inactivity.
Endpoints Encryption
Entity requires that all critical endpoints are encrypted to protect them from unauthorized access.
Mobile Device Management (MDM)
Corporate endpoints are centrally managed through a Mobile Device Management (MDM) solution that enforces security configurations, including disk encryption, screen-lock, OS-update, and compliance policies.
Corporate security (35)
Code of Business Conduct
Entity has a documented policy to define behavioral standards and acceptable business conduct.
Organizational Structure
Entity maintains an organizational structure to define authorities, facilitate information flow and establish responsibilities.
Roles & Responsibilities
Entity has established procedures to communicate with staff about their roles and responsibilities.
Competency Screening
Entity has procedures to ensure that all security-related positions are staffed by qualified individuals who have the necessary skill set.
Personnel Screening
Entity has established procedures to perform security risk screening of individuals before authorizing access.
New Hire Policy Acknowledgement
Entity has established procedures for new staff to acknowledge applicable company policies as a part of their onboarding.
Security & Privacy Awareness
Entity provides information security and privacy training to staff that is relevant to their job function.
Performance Review
Entity requires that all employees in client serving, IT, Engineering, and Information Security roles are periodically evaluated regarding their job responsibilities.
Periodic Policy Acknowledgement
Entity has established procedures for staff to acknowledge applicable company policies periodically.
Automated Reporting
Entity has provided information to employees, via various Information Security Policies/procedures, on how to report failures, incidents, concerns, or other complaints related to the services or systems provided by the entity in the event there are problems.
Incident Reporting Assistance
Entity has provided information to customers on how to report failures, incidents, concerns, or other complaints related to the services or systems provided by the Entity in the event there are problems.
Risk Framing
Entity performs a formal risk assessment exercise annually, as per documented guidelines and procedures, to identify threats that could impair systems' security commitments and requirements.
Risk Assessment
Each risk is assessed and given a risk score in relation to the likelihood of it occurring and the potential impact on the security, availability, and confidentiality of the Company platform. Risks are mapped to mitigating factors that address some or all of the risk.
Fraud
Entity considers the potential for fraud when assessing risks. This is an entry in the risk matrix.
Third-Party Criticality Assessments
Entity performs a formal vendor risk assessment exercise annually to identify vendors that are critical to the systems' security commitments and requirements.
Assigned Cybersecurity & Privacy Responsibilities
Entity's Senior Management assigns the role of Information Security Officer who is delegated to centrally manage, coordinate, develop, implement, and maintain an enterprise-wide cybersecurity and privacy program.
Internal Audit using Sprinto
Entity uses Sprinto, a continuous monitoring system, to track and report the health of the information security program to the Information Security Officer and other stakeholders.
Periodic Review & Update of Cybersecurity & Privacy Program
Entity's Senior Management reviews and approves the state of the Information Security program including policies, standards, and procedures, at planned intervals or if significant changes occur to ensure their continuing suitability, adequacy, and effectiveness.
Management Review of Org Chart
Entity's Senior Management reviews and approves the Organizational Chart for all employees annually.
Management Review of Risks
Entity's Senior Management reviews and approves the "Risk Assessment Report" annually.
Management Review of Third-Party Risks
Entity's Senior Management reviews and approves the "Vendor Risk Assessment Report" annually.
Subservice organization evaluation
Entity reviews and evaluates all subservice organizations periodically, to ensure commitments to Entity's customers can be met.
Segregates Roles and Responsibilities
Entity's Senior Management segregates responsibilities and duties across the organization to mitigate risks to the services provided to its customers.
Testing
Entity has procedures to conduct regular tests and exercises that determine the effectiveness and the readiness to execute the contingency plan.
Asset Ownership Assignment
Entity has set up mechanisms to assign and manage asset ownership responsibilities and establish a common understanding of asset protection requirements.
Data Governance
Entity maintains a list of legal, statutory, and regulatory requirements relevant to information security.
New Hire Security & Privacy Training Records
Entity has established procedures for new staff to complete security and privacy literacy training as a part of their onboarding.
Periodic Security & Privacy Training Records
Entity documents, monitors, and retains individual training activities and records.
Updates During Installations / Removals
Entity periodically updates and reviews the inventory of systems as a part of installations, removals, and system updates.
Inventory of Endpoint Assets
Entity develops, documents, and maintains an inventory of organizational endpoint systems, including all necessary information to achieve accountability.
Subprocessors
Haber engages a limited set of subprocessors to deliver its services and performs security, privacy, and legal due diligence before onboarding any new vendor.
Email Protection
Haber uses Google Workspace for corporate email, secured with TLS encryption in transit and multi-factor authentication for account access. Email authentication is enforced to prevent spoofing, and protections against phishing, malware and spam across all mail.
Phishing & Social Engineering Training
As part of annual security awareness training, Haber educates personnel on phishing, smishing, and social-engineering techniques. Simulated phishing campaigns are run to reinforce awareness, help employees recognize red flags, and ensure they know how to report suspected attempts to the security team.
Incident Response
Haber maintains a documented incident management procedure covering all phases of the response process that includes identification, validation and severity assignment, containment and resolution, root-cause analysis, and post-incident communication. The procedure defines roles and responsibilities, and the incident response plan is tested as part of Haber's annual business continuity and disaster recovery exercises.
Internal Single Sign-On (SSO)
Haber uses Google Workspace as its internal identity provider, enabling single sign-on across supported corporate applications. This centralizes authentication and access management and supports consistent enforcement of multi-factor authentication.
