Security at Akoben

Akoben processes transaction data for banks, fintechs, payment service providers and mobile money operators, which makes the security of the platform part of the product rather than a page about it. This page states what is in place today. Where a control is narrower than the term usually implies, it says so.

Encryption

Transaction data is encrypted in transit using TLS, and encrypted at rest. In hosted deployments Akoben manages the encryption keys. Customer-managed keys are not currently offered.

Authentication

Multi-factor authentication is available and can be enabled for users. It is not enforced by default, so an institution that requires a second factor for all personnel should turn it on during onboarding rather than assume it is already on.

Single sign-on is supported through SAML and OpenID Connect, so customers can connect their own identity provider and keep password policy, session rules and account lifecycle in the system they already run. For most institutions this is the more useful of the two controls, because it puts joiners, movers and leavers under an existing process instead of a second one.

Access control

Akoben ships a fixed set of roles. A user is assigned a role, and that role determines what they can see and which actions they can take.

Two limits are worth stating plainly. Customers cannot define their own roles, and there is no data scoping that would limit a user to a subset of accounts, channels or portfolios. If your separation-of-duties model depends on either, raise it before procurement rather than after.

Audit logging

Akoben records every action taken in the product to an audit log. The log is retained, and it is immutable: entries cannot be altered or removed after the fact.

That matters more than it sounds on a fraud platform. A supervisor asking about a particular transaction is rarely asking whether it was monitored, which is assumed. They are asking who reviewed it, when, what they saw and what they concluded. A log that can be edited answers none of those questions, however complete it looks.

Secure development

Three practices apply to every change:

They are listed individually rather than summarised, because a due-diligence questionnaire asks for them individually.

Penetration testing

The platform is tested annually by an independent third party, and the report is available to customers and prospective customers on request.

Independent is the operative word. Internal testing finds what the people who built the system already thought to look for.

Backups and recovery

Backups are taken, and restores are tested rather than assumed. Recovery time and recovery point objectives are defined and available on request.

Tested restores are the part worth comparing between vendors. Most can say they take backups. Fewer can say they have proven they can put them back.

Data residency and tenant separation

Customers can choose the region in which their data is held, and each tenant's data is isolated from every other tenant's.

Region choice is one of two ways deployment answers a residency requirement. The other is to move the deployment itself, which the next section covers.

Incident response

Akoben operates a defined security incident process, including a committed timeframe for notifying affected customers. The specific commitment is set out in the customer agreement.

What deployment changes

Where Akoben runs affects several of the controls above. In a hosted deployment, Akoben operates the infrastructure, manages the keys and takes the backups. Where Akoben is installed in a customer's own cloud account or in their own data centre, that boundary moves, and so does responsibility for the infrastructure beneath the application.

Neither arrangement is more secure than the other in the abstract. They place control and obligation in different places, which is a decision for an institution's own risk function rather than a product question.

Asking for more detail

Security questionnaires are expected and answered. Where a specific control is not described here, the reason is usually that it needs a longer answer than a public page can carry, not that the question is unwelcome.

Common questions

Is Akoben certified to a recognised security standard?

Akoben holds ISO 27001 certification. The certificate, the certifying body and the scope statement are available on request, and the scope is the part worth reading: certification covering part of a business is a different assurance from one covering the product and the infrastructure it runs on. Certification shows that an audited information security management system exists, not that any single control works a particular way, which is why the individual controls are listed on this page.

Akoben does not hold SOC 2 or PCI DSS. Where a procurement process requires either, it is worth saying so early — that is a shorter conversation than discovering it midway through due diligence.

Where is transaction data stored?

That is a deployment decision rather than a fixed property of the product. In a hosted deployment, customers choose the region their data is held in, and each tenant's data is isolated from every other tenant's. Where Akoben is installed in a customer's own cloud account or their own data centre, the data never leaves infrastructure the institution already controls. Either way, the data Akoben evaluates is the transaction data the connected systems send it, encrypted in transit and at rest.

Regulatory and data residency requirements are usually what decides this, rather than a technical preference. An institution that must keep transaction data inside a particular jurisdiction can satisfy that either by region choice in a hosted deployment or by taking the deployment in-house entirely.

Who can see transaction data inside Akoben?

Access is controlled by a fixed set of roles that ship with the product. A user is assigned a role, and the role determines what they can see and do. Customers cannot currently define their own roles, and there is no per-user scoping that would restrict an investigator to a subset of accounts, channels or portfolios. Every action a user takes is written to an audit log that cannot be altered afterwards.

This is worth checking against your own separation-of-duties requirements before procurement rather than during it. An institution that needs investigators partitioned by portfolio, or that needs to define its own roles, will find fixed roles a constraint.

Discuss your transaction monitoring requirements

Tell us which transaction flows you need to monitor, which systems Akoben would integrate with, and how your fraud team works today.

Request a demo