Information security is the set of policies, controls, and day-to-day habits that keep data safe from loss, theft, or misuse. For a FinTech firm, a law practice, or an accountancy, that data is client records, financial information, and case files. Done well, it is invisible and simply part of how the firm works. Done badly, it is the reason a regulator, an insurer, or a client starts asking hard questions.

What information security covers

Technical controls such as firewalls and encryption are one part of it. Physical controls matter too, such as who can walk into your server room, and so do human habits, such as whether staff can recognise a phishing email.

ISO/IEC 27001, the best-known standard for managing information security, frames the goal as protecting the confidentiality, integrity, and availability of data, and it applies to information in all forms, including paper-based, cloud-based, and digital data. Confidentiality means only the right people see the data. Integrity means it stays accurate and unaltered. Availability means you can get to it when you need it.

Why regulated firms carry a heavier burden

The data regulated firms hold is more sensitive, and the consequences of losing it are worse. Law firms hold privileged client correspondence. Accountancies hold financial records that can read as a map of someone’s whole life. Healthcare providers hold medical history. FinTech firms hold financial data and the personal details needed to move money. Each of these sectors has a regulator or professional body that expects the data to be handled properly, and clients who assume it already is.

The gap between a policy and a working control

Some firms have an information security policy sitting in a folder, signed off years ago and untouched since. A policy says what should happen. A control makes it happen, gets checked, and gets fixed when it stops working. A policy is written once, but a control has to be run, checked, and fixed for as long as the policy exists. To tell which you have, ask who checked it was followed last month, and what they found.

Where vulnerability management fits in

Controls only work if you know what you are protecting and where it is weak. That is the job of vulnerability management, the continuing process of finding weaknesses in your systems, working out which ones matter, and fixing them in order of priority. It runs as a cycle, because new weaknesses appear as software changes and new threats emerge. A single scan before an audit leaves the same gap as a policy nobody has opened since it was signed.

Building towards a recognised standard

Some regulated firms go on to formal certification, usually ISO 27001, as proof that their information security goes beyond good intentions. Certification is the end point of that work. It needs working controls, clear ownership, and an honest view of your own risks first, or it becomes a scramble. FinTech firms facing scrutiny from regulators and investors can read more in the page on ISO 27001 for FinTech firms.

Getting the right help at the right time

A smaller regulated firm may have no in-house security specialist and does not need one to get started. It needs an honest view of where it stands, specific to its sector. Outside help can move you from assuming your controls work to knowing they do, with evidence you can show. Choose the adviser carefully, because the wrong fit at this stage costs time and money to correct.

If you are not sure your current controls would hold up to scrutiny, read what to look for in a cyber security consultant before you commission anyone.