Security, Integration and Deployment

Your data stays where your regulator says it must

Eagle-Eye runs in your environment: in your data centre, in your private cloud or with a dedicated hosting provider you approve, under your access policies, with every action on record.

Deployment and data residency

Your environment, your data sovereignty

On premises

In your own data centre, on servers you run.

Full physical control

Private cloud

In your own cloud tenancy, in the region you choose.

Your provider, your region

Dedicated hosting

A single-tenant environment at a hosting provider you approve.

Isolated environment
In every option
  • The instance serves your institution alone
  • Your data stays in the jurisdiction you choose
  • Your security and access policies apply
Security controls

Safeguards built into the platform

Access by permission

Access is granted permission by permission, not by fixed role, and maker-checker control separates the person who proposes from the person who approves.

SSO and MFA

Single sign-on through your organization's identity provider, and multi-factor authentication, so a stolen password alone does not open an account.

Password policy

Configurable to your organization's password policy.

Encryption at rest and in transit

Data is encrypted when it is stored and while it moves between systems.

Built under a SecDevOps lifecycle
  • Static application security testing (SAST) of the source code
  • Dynamic application security testing (DAST) of running builds
  • Security gates in the CI/CD pipeline that hold a release until findings are resolved
Integration and implementation

Connects to your systems as they are

Eagle-Eye takes customer and transaction data as your systems send it, and returns its decisions to where your team works.

APIs

Real-time screening and risk scoring for onboarding and transactions, answered in milliseconds.

File-based data transfer

Scheduled or on-demand exchange of customer and transaction data as files, for systems without an API.

Core and channel systems

Works with core banking, remittance, insurance and e-wallet platforms.

Watchlist providers

Official lists, plus any paid or custom list provider you use.

How implementation runs

  1. ScopeYour obligations, data sources and the channels to screen and monitor.
  2. DeployOn premises, in your private cloud or with dedicated hosting.
  3. IntegrateAPIs and file-based data transfer with your core and channel systems, and your lists connected.
  4. ConfigureScreening templates, risk model, scenarios, workflows and permissions, set by your compliance team without code.
  5. ValidateTesting on your own data and tuning thresholds before go-live.
  6. Go liveTraining for your teams and continued support after go-live.

What we need from you

  • EnvironmentYour servers, your cloud tenancy, or approval of a dedicated hosting provider
  • DataAccess to customer and transaction data, and a sample for testing
  • ListsThe list subscriptions your institution holds
  • PeopleA project owner from compliance and one from IT
Plan an implementation with us