The Craft Series

A policy nobody follows is decoration

The Craft Series: A policy nobody follows is decoration

A security policy earns its keep when it describes how you actually work, names owners and leaves evidence behind.

At Circle Square, a lot of our security and compliance work starts with reading. Before we can protect a business, we need to understand what it has already promised to do, and those promises usually live in a set of policies. Some of the best-written policies I’ve seen belong to businesses that follow very few of them.

That isn’t a criticism. It’s one of the most common situations we walk into. The policies are well formatted and carefully worded. Someone paid for them, or started from a template and put the company logo on the cover. Then they went into a shared folder while everyone got back to running the business.

A policy in that state is mostly decoration. It looks fine on the shelf. It doesn’t help much when something goes wrong, and it can create real trouble when someone outside the business asks you to prove what it says.

What a working policy does

A working policy describes how the business actually runs. Not an ideal version, and not how a template author imagined some other company runs. If your access policy says accounts are removed the day someone leaves, that needs to be what happens, or the policy needs to say what happens instead.

A working policy names owners: a person, by role, who is responsible for making the thing happen and who answers when it doesn’t. “IT” or “management” isn’t an owner. I spent six years as a crew chief in the Air Force, and the rule there was simple. Every aircraft has an owner, and every job is signed for. Policies work the same way. A task without an owner tends to become a task nobody does.

And a working policy produces evidence. Training records that show who completed security training and when. Access reviews that show someone looked at who has access to what and made decisions about it. Logs that show the controls were running. Without that trail, it’s hard to show anyone the policy was followed, including yourself.

Who is asking for the evidence

The audience for your policies has grown. A policy binder used to exist mostly for an auditor in a regulated industry. Now the questions come from several directions.

Your cyber insurer asks. The renewal form wants to know whether you do specific things, and more often it wants to know you can show it. Your larger clients ask, through vendor questionnaires and contract terms. Regulators ask, if your industry has them.

Each of those audiences looks past the document to the evidence behind it. A policy that says you review access quarterly is only as strong as the four review records you can produce for the last year.

That’s why our compliance work is built around a simple idea: evidence organized before anyone asks for it. The week a questionnaire is due or a claim is being reviewed is a stressful time to find out the policies and the reality drifted apart.

Mapped to something recognized

A working policy also needs a backbone. We map the policies we build to two recognized frameworks, NIST CSF 2.0 and CIS Controls v8.1. That gives the policy a structure other people already understand. When an insurer or a client asks how you handle a given area, you can point to where it lives and what evidence supports it.

A framework helps in another way, too. It shows you the gaps. Covering only what you already do well is natural. A framework gently makes sure the rest gets looked at.

I sometimes think of it like the difference between a watch kept in a drawer and one worn every day. The everyday one earns its value by holding up. A security policy deserves the same test: does it hold up when it’s carried, every day, by the people who actually run your business?

If your policies are sitting in a folder, that’s a very fixable problem. Start by reading one against what really happens in your office. Whatever gap you find is the work, and it’s usually smaller than people fear. If you’d like a second set of eyes on it, we’re always glad to help.

One standard. Every client. The door is always open.

If you want policies your team follows and evidence that’s ready for the audit, the exam and the renewal questionnaire, our compliance consulting team can help. circlesquareconsulting.com/compliance-consulting

Newsletter

The Hour.

One email a month from Mike: one idea, one thing to check, and one story from the field. Under 400 words.

The Hour, once a month

Find out what an hour costs you.

Book a Downtime Ledger

About 60 minutes. Your numbers. You keep the result.