Led by a founder with more than 21 years of experience

contact@guilda.io

Financial Services

Cybersecurity for financial services

Money and customer data move through systems that attackers probe every day and examiners review every year. We help banks, lenders and fintechs see what happens in those systems, act on it, and show the evidence when they are asked.

Overview

A financial institution is attacked and examined at the same time. Criminals go after the places where money moves: customer sign-ins, transfer requests, the accounts that run the core platform. Examiners and auditors ask a different question about the same systems: can you show who did what, when you noticed and what you did about it? Most institutions find that the answer to both lies in the same logs.

What attackers want from a financial institution

The direct route is the customer's account. With a reused password or an intercepted code, an attacker signs in to online banking and moves money before anyone calls. The indirect route runs through staff: a convincing request to change a supplier's bank details, or a wire that seems to come from an executive. The slowest and most damaging route is inside the network, where attackers collect administrator credentials, find the core systems and the backups, and wait.

Each route leaves traces, but in different places. Customer sign-ins are recorded by the digital channels, transfers by the payment systems, administrator activity by the directory and the servers. Read separately, none of these records looks alarming. Read together, a new device, a changed phone number and an unusual transfer on the same account tell a clear story.

One view of core systems, digital channels and privileged access

That is the work we did for a large financial institution in the United States. We implemented a SIEM inside the institution's own environment and connected the core banking and payment systems, online and mobile banking with their web and API servers, staff and administrator sign-ins with the directory and privileged accounts, and the branch and data-centre networks, firewalls, cloud accounts and staff computers. We wrote the alert rules for the way attacks reach a financial institution, tested them and handed the platform to its team with runbooks. Threats it could not see before are now detected and raised. The service behind it is Threat Detection & SIEM Implementation.

Detection works best inside a security program that someone owns. Security Governance builds that program, with the policies, risk assessments, supplier reviews and board reporting that regulators look for. Red Teaming & Penetration Testing tests the digital channels, partner APIs and internal network before an attacker does. Cybersecurity Training prepares the people who receive fraudulent transfer requests.

What examiners expect to see

The rules differ by country and by type of institution, but they share a theme. In the United States, the GLBA asks for a written security program and the FTC's Safeguards Rule asks for logs of what authorised users do. New York's Part 500 requires audit trails, monitoring and a notice to the Department within 72 hours of determining that an incident has occurred, and public companies test the IT controls behind their financial reporting under Sarbanes-Oxley. In Mexico, the CNBV requires banks to keep and review audit records, correlate detection with them and report incidents immediately, and the Fintech Law has the CNBV set comparable rules for fintech institutions.

We don't certify or audit against any of these rules, and we don't sell PCI DSS work. The standards we work with directly are ISO/IEC 27001, SOC 2 and NIST. What we build is the logging, detection and documentation that makes those requirements possible to meet and possible to show.

Your data stays in your environment

Logs from a financial institution contain customer and account data, so how a provider handles them matters as much as what it builds. The SIEM runs in your own cloud tenant or data centre, and the logs stay there. Access for our engineers is named, limited to the project and removed at handover. We complete your vendor-risk process before work starts, and we keep no copy of your data when we leave.

Threat landscape

What attackers go after

Customer account takeover

Criminals sign in to online and mobile banking with passwords stolen from other sites, intercepted one-time codes or a phone number moved to a new SIM. Once inside, they change contact details and move money quickly, so the sign-in pattern is often the only early warning.

Fraudulent payments and transfers

An email that seems to come from a client, an executive or a supplier asks for an urgent transfer or new account details. Payment fraud often succeeds without any malware at all, and it is caught only when payment systems and mailboxes are watched together.

Ransomware against core and branch systems

A financial institution cannot stop serving customers for a week, and attackers know it. Ransomware groups target core platforms, branch networks and backups, usually after weeks spent inside the network, collecting credentials and finding the systems that matter.

Misuse of privileged accounts

Administrator and service accounts can reach customer data, payment systems and the logs that would show their misuse. Whether the account was stolen or an insider is abusing their own access, the signs are in the directory and in what those accounts do after they sign in.

Providers and fintech connections

Core processors, card processors, cloud services and fintech partners connect through APIs and remote access. Each connection carries trust that an attacker can borrow, and a provider's breach can expose an institution's customers without anyone touching its own network.

Compliance

The regulatory landscape, mapped

The rules Financial Services answer to, what each demands and how we help
RuleWhereWhat it demandsHow we help
GLBA Safeguards RuleUnited StatesFinancial institutions must protect customer information with a written security program. The FTC's Safeguards Rule, for institutions outside the banking agencies, requires a qualified individual in charge, logging of authorised users' activity, testing, oversight of service providers, a written report to the board at least once a year and notice to the FTC of certain breaches.A SIEM with documented sources and alerts covers the logging and monitoring part, and our governance work builds the written program around it.
NYDFS cybersecurity regulation (23 NYCRR Part 500)United StatesCovered entities in New York must keep audit trails that can detect and respond to cybersecurity events, monitor what authorised users do, notify the Department within 72 hours of determining that a cybersecurity incident has occurred, and file a certification of compliance, or an acknowledgment of noncompliance, every year by April 15. Larger companies must also run centralised logging with security event alerting.Centralised logging with alerting is what we implement, and the rule documentation and runbooks show how events are detected and handled.
Sarbanes-Oxley Act, section 404United StatesPublic companies must report each year on their internal control over financial reporting, and at larger companies the auditor also attests to it. The IT controls behind the financial systems, such as who can access them and how changes and activity are recorded, are part of what is tested.Logs of access and changes to financial systems, kept and reviewed in one place, give your auditors something they can test.
CNBV rules for banks (articles 168 Bis 11 to 17)MexicoBanks in Mexico must run an information security control system under a security master plan and a chief information security officer, keep audit records of access and user activity and review them, correlate automated detection with those records, test their defences and report security incidents to the CNBV immediately.We build the logging, correlation and alerting these articles describe, and the runbooks that start an incident report on time.
Mexico's Fintech Law (article 48)MexicoUnder the law that regulates financial technology institutions, the CNBV, and for electronic payment funds the CNBV together with Banco de México, set the information security rules those institutions must follow, including records of their transactions.Whatever the rules require you to record, a SIEM keeps it searchable and raises an alert when something in it looks wrong.
PCI DSS v4.0.1InternationalAn institution that issues, acquires or processes payment cards must protect card data under the card brands' data security standard, which includes logging and monitoring all access to cardholder data and testing security regularly.For context: we do no work under this rule

Services

The services for this sector

Threat Detection & SIEM Implementation

Core banking, digital channels and privileged accounts each keep their own logs. A SIEM correlates them, so account takeover, payment fraud and misuse of access raise alerts your team can act on, with the records examiners ask for.

Security Governance

The GLBA, NYDFS and the CNBV all expect a written security program with someone in charge, risk assessments, supplier oversight and reports to the board. We design that program on ISO/IEC 27001 and NIST CSF.

Red Teaming & Penetration Testing

Regulators expect regular testing. We test online and mobile banking, the APIs partners use and the internal network the way an attacker would, and retest once the findings are fixed.

Cybersecurity Training

Fraudulent transfer requests and phishing reach staff before they reach any system. Training and phishing exercises for branch, operations and finance staff make them harder to fall for.

Example project

Threat detection across a financial institution's core, digital and privileged systems

We implemented a SIEM inside the institution's own environment and connected four groups of sources. These were the core banking and payment systems, covering transfers and cards; online and mobile banking with their web and API servers; staff and administrator sign-ins, the directory and privileged accounts; and the branch and data-centre networks, firewalls, cloud accounts and staff computers. We wrote alert rules for the attacks that target a financial institution through each group, tested them and handed the platform to the institution's team with runbooks.

Client
A large financial institution in the United States
Result
Threats the institution could not see before are now detected and raised to its team, from customer channels to administrator accounts.

FAQ

Frequently asked questions

Can the SIEM give us the logging evidence examiners and auditors ask for?

It can produce it. Examiners and auditors want to see that security events are recorded, kept for the required period and reviewed, and that alerts lead to action. We design the sources, retention and alert handling with your requirement in hand and document them. Whether it satisfies a given rule is for your examiner or auditor to decide.

Where do our logs live, and who at GUILDA can see them?

In your environment. The SIEM runs in your own cloud tenant or data centre, and the logs do not leave it. Only the GUILDA engineers named for the project have access, for the length of the project, and that access is removed at handover. We go through your vendor-risk process before we get any access, and we keep no copy of your log data afterwards.

Can you hand the SIEM to our own team or our existing SOC provider?

Yes, that is how every project ends. We don't run a monitoring service ourselves. If your own team watches the alerts, they receive the runbooks and a walkthrough. If a managed provider does, we write the runbooks for them and include them in the handover, so they start with the same knowledge as your staff.

Do you work with banks and fintechs in Mexico?

Yes. We work in English and in Spanish, from offices in Fort Lauderdale and Zapopan, and you can write to us in Spanish at contacto@guilda.mx. For an institution supervised by the CNBV, the audit records, detection and incident reporting its rules require are part of what the work is designed around.

Next step

Tell us what your examiners ask for

Name the systems involved, the rules you answer to and any exam or audit date coming up. We reply within two business days.