Skip to content
Security & Compliance

A security checklist for financial applications before go-live

What we check before a financial system goes to production: access control, audit trails, auditable test documentation, and day-one readiness.
Article cover: a security checklist for financial apps before go-live
CategorySecurity & Compliance
Published
Reading time3 min read
AuthorYogi Chandra Saputra, President Director

Go-live day is the busiest day of a project and the worst day to find a security hole. In a financial application more than reputation is at stake: money moves, customer data is stored, and at some point an examiner will ask for evidence.

The checklist below is the one we run before handing a system over to production. It is a set of questions that need clear answers before anyone presses the release button.

Control who gets in, and how far

The first question is always the same: who has access to the production environment, and why. Access is scoped per environment and per person. Developer accounts are not used in production, test and production credentials are kept apart, and an account that is no longer needed is closed the day its owner moves on, without waiting for the end of the month.

On the user side, access levels follow the client’s organisational structure, even when that is not the easiest thing to implement. A compliance unit does not need to see disbursement data, and a branch officer does not need to change system parameters. This kind of separation is far cheaper to build before release than to tidy up after an incident.

Also check the paths people forget: direct database access, access to backup files, and credentials embedded in automation scripts. These routinely fall outside the formal access list, even though each of them opens the same door just as wide. Record who owns each path, and give every credential a rotation schedule so it does not stay on the value it was given at installation.

Make sure every change leaves a trail

Financial systems are examined after the event, so an audit trail is mandatory. Every transaction, approval and parameter change needs to be recorded with who did it, when, and the values before and after.

What often gets missed is who can change the trail itself. During an examination, a record its own users cannot edit is far more useful than a complete log that can be rewritten. Confirm this with a dedicated test.

Test with documentation that can be audited

In an audit, testing that was never documented counts as testing that never happened. So before handover we make sure the test documentation set is complete and can be read by somebody who did not work on the project.

  • A test plan stating the scope, the environments and the test data used.
  • A test procedure per scenario, covering the happy path and failure scenarios.
  • A test log with the result of every scenario and the date it was run.
  • A UAT record signed by both parties.
  • A list of open findings with the decision made: fixed before release, or accepted with a written mitigation.

The signed UAT record is the basis for handover. Where an item is still open, write it down as it is, together with the plan to close it. A finding hidden on release day reappears at a far more expensive moment.

Prepare the first day after go-live

Before the first user signs in, make sure monitoring is running, the escalation path is clear, and the number to call during an incident is already at hand. The backup restore procedure should already have been rehearsed.

Agree as well who may make decisions when an incident happens outside working hours, and how far those decisions may go without waiting for a meeting. In a first incident the difficulty is usually more about authority than technology: who is allowed to press the button.

Finally, agree the service level in writing: service hours, response time and resolution time per incident level. Financial systems run for years after go-live, and their security depends on how they were built and also on how they are maintained.

ShareLinkedInWhatsAppX

Have a system to discuss? Talk to us.

We look at your requirements and put together a clear plan. The first session is free.