Information security is the practice of protecting information, in any form, against unauthorised access, use, disclosure, alteration or destruction. It covers paper records and spoken information as well as data held in computer systems, and it applies to every organisation, but it is especially important for banks, payment providers and market infrastructures whose business consists largely of records of who owns what.
The term overlaps with cybersecurity, which focuses on threats arriving through networks and connected systems. Information security is the broader discipline: it includes physical protection of buildings and media, staff vetting and training, supplier management and legal agreements. Within financial firms it is usually treated as part of operational risk and overseen by a chief information security officer reporting to senior management and the board.
Core principles
Information security is traditionally defined through three properties, often called the CIA triad:
- Confidentiality. Information is disclosed only to authorised people, processes and systems, for example through access control and encryption.
- Integrity. Information is accurate and complete and has not been altered without authority, which is supported by checks such as hashing, digital signatures and reconciliations.
- Availability. Information and systems can be used when needed, which depends on resilient design, backups and recovery plans.
Further properties are often added, notably authenticity, accountability and non-repudiation, which matter in payment messaging where a bank must be able to prove that an instruction came from a given sender and was not changed in transit.
Standards and frameworks
The most widely used international standard is ISO/IEC 27001, which sets requirements for an information security management system: a structured way to identify risks, choose controls, assign responsibility and improve over time. Organisations can be certified against it by accredited bodies. The companion standard ISO/IEC 27002 gives guidance on individual controls, and ISO/IEC 27005 covers information security risk management. In the United States, the Cybersecurity Framework published by the National Institute of Standards and Technology is widely used by financial firms and regulators.
Sector frameworks build on these. The Payment Card Industry Data Security Standard sets detailed rules for anyone that stores, processes or transmits card data. SWIFT requires its users to attest each year against a set of security controls. For market infrastructures, the Principles for Financial Market Infrastructures require a robust operational risk framework, and CPMI and IOSCO issued specific guidance on cyber resilience for FMIs in 2016.
Typical controls
A security control is any measure that reduces risk to information. Controls are often grouped as preventive, detective or corrective, and as technical, organisational or physical. Common examples in financial firms include role-based access with multi-factor authentication, segregation of duties, network segmentation and firewalls, an intrusion detection system, logging and an audit trail, encryption of data at rest and in transit, secure software development, vulnerability management, staff awareness training and tested backup and recovery arrangements. The choice and strength of controls follow from a risk assessment rather than a fixed checklist.
Regulation in financial services
Supervisors increasingly set binding requirements. In the European Union, the Digital Operational Resilience Act (DORA), which has applied since 17 January 2025, sets common rules on ICT risk management, incident reporting, resilience testing and oversight of critical third-party ICT providers for banks, insurers, investment firms, payment institutions and market infrastructures. Data protection laws such as the General Data Protection Regulation add duties on the security of personal data and on breach notification. In the United Kingdom, regulators approach the topic through their operational resilience rules, which require firms to stay within impact tolerances for important business services.
Why it matters for payment and settlement systems
Payment and settlement systems concentrate risk. A compromised participant can send fraudulent payment instructions that settle with finality within seconds, and a corrupted ledger at a central securities depository could undermine confidence in ownership records across a whole market. Incidents in which attackers used stolen credentials to send fraudulent interbank payment messages showed that weaknesses at one institution can be exploited through a shared network. For this reason, infrastructures set security requirements for their participants, monitor message flows for anomalies and design recovery arrangements so that critical operations can resume quickly, while preserving the integrity of data, after a disruptive event. Security and resilience are therefore treated as conditions of participation rather than as matters for each firm alone.
External links
Ref 1050000749