top of page

Security and privacy at idPair

Image by Vazgen

Security is at the heart of what we do. The integrity of the services we provide depends on our ability to keep data safe.

Governance

Security and Compliance at idPair

idPair is undergoing a SOC 2 Type II attestation and undergoes security testing via GLI.

idPair's Security and Privacy teams establish policies and controls, monitor compliance with those controls, and prove our security and compliance to third-party auditors.

 

Our policies are based on the following foundational principles:

01.

Access should be limited to only those with a legitimate business need and granted based on the principle of least privilege.

02.

Security controls should be implemented and layered according to the principle of defense-in-depth.

03.

Security controls should be applied consistently across all areas of the enterprise.

04.

The implementation of controls should be iterative, continuously maturing across the dimensions of improved effectiveness, increased auditability, and decreased friction.

Data at rest

All datastores with customer data, in addition to S3 buckets, are encrypted at rest. Additionally, sensitive data is protected with field-level encryption.
​
This means the data is encrypted even before it hits the database so that neither physical access, nor logical access to the database, is enough to read the most sensitive information.

Data in transit

idPair uses TLS 1.2 or higher everywhere data is transmitted over potentially insecure networks. We also use features such as HSTS (HTTP Strict Transport Security) to maximize the security of our data in transit. Server TLS keys and certificates are managed by AWS and deployed via Application Load Balancers.

Secret management

Encryption keys are managed via AWS Key Management System (KMS). KMS stores key material in Hardware Security Modules (HSMs), which prevents direct access by any individuals, including employees of Amazon and idPair. The keys stored in HSMs are used for encryption and decryption via Amazon’s KMS APIs.
​
Application secrets are encrypted and stored securely via AWS Secrets Manager and Parameter Store, and access to these values is strictly limited.
 

Product Security

Penetration Testing

idPair engages with one of the best penetration testing consulting firms in the industry at least annually. Our current preferred penetration testing partner is GLI - Bulletproof, one of the leading experts in security.  

All areas of the idPair product and cloud infrastructure are in-scope for these assessments, and source code is fully available to the testers in order to maximize the effectiveness and coverage.

We make summary penetration test reports available upon request.

Enterprise Security

Identity and access management

idPair uses Microsoft to secure our identity and access management. We enforce the use of phishing-resistant authentication factors wherever possible.

idPair employees are granted access to applications based on their role, and automatically deprovisioned upon termination of their employment. Further access must be approved according to the policies set for each application.

Secure remote access

idPair secures remote access to internal resources. We also use malware-blocking DNS servers to protect employees and their endpoints while browsing the internet.

Security education

idPair provides comprehensive security training to all employees upon onboarding and annually through educational modules. In addition, all new employees attend a mandatory live onboarding session centered around key security principles. All new engineers also attend a mandatory live onboarding session focused on secure coding principles and practices.

idPair's security team shares regular threat briefings with employees to inform them of important security and safety-related updates that require special attention or action.

Vendor Security

idPair uses a risk-based approach to vendor security. Factors which influence the inherent risk rating of a vendor include:

​

- Access to customer and corporate data

​

- Integration with production environments

​

- Potential damage to the idPair brand

​

Once the inherent risk rating has been determined, the security of the vendor is evaluated in order to determine a residual risk rating and an approval decision for the vendor.

Data Privacy

bottom of page