Governance

Fintegrate’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:

1. Access should be limited to only those with a legitimate business need and granted based on the principle of least privilege.
2. Security controls should be implemented and layered according to the principle of defense-in-depth.
3. Security controls should be applied consistently across all areas of the enterprise.
4. The implementation of controls should be iterative, continuously maturing across the dimensions of improved effectiveness, increased auditability, and decreased friction.

 

Security and Compliance at Fintegrate

Fintegrate maintains a SOC 2 Type II attestation (in observation period).  Our SOC 2 Type II report is available upon request.

Data protection

Data at rest

Fintegrate does NOT store customer data.  While we store customer access credentials for our integrations, all data transported by Fintegrate never touches Fintegrate databases.  

Data in transit

Fintegrate 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 Linode and deployed via Application Load Balancers.

Product security

Penetration testing

Fintegrate’s current preferred penetration testing partner is Crowdstrike.

All areas of the Fintegrate 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.

Vulnerability scanning

Fintegrate requires vulnerability scanning at key stages of our Secure Development Lifecycle (SDLC):

Static analysis (SAST) testing of code during pull requests and on an ongoing basis

Software composition analysis (SCA) to identify known vulnerabilities in our software supply chain

Malicious dependency scanning to prevent the introduction of malware into our software supply chain

Dynamic analysis (DAST) of running applications

Network vulnerability scanning on a
period basis

External attack surface management (EASM) continuously running to discover new external-facing assets

Enterprise security

Vendor security

Fintegrate 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 Fintegrate 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.

Security education

Fintegrate provides comprehensive security training to all employees upon onboarding and annually through educational modules within Fintegrate’s own platform. In addition, all new employees attend a mandatory live onboarding session centered around key security principles. 

Fintegrate’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.

Identity and access management

Fintegrate 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.

Regulatory compliance

Fintegrate evaluates updates to regulatory and emerging frameworks continuously to evolve our program.