The problem: Your delivery team works inside the client’s office, on the client’s laptops and network. It is not clear whose security rules apply: yours or the client’s. The client says, “You are on our site, follow our rules.” Your own security says, “They are our staff, follow ours.” The team is stuck in the middle.
Words used here: a rule book is the set of security rules a company expects people to follow. Client site means working at the client’s office or on the client’s systems. Conduct means how people behave, such as how they handle data and passwords.
Think of a guest chef in someone else’s kitchen
A chef is hired to cook at a friend’s house. The host has rules: shoes off, no raw meat on the table, lock the back door. The chef has habits of their own: wash hands often, keep food covered. Mostly the two agree. But on the day they do not, the chef has to guess which rule wins.
What it looks like at work
A team of six works at the client’s office for four months. They use laptops given by the client, which block USB drives and some websites. They also keep a few files on their own company laptops, which are not covered by the client’s controls. One developer asks, “Can I copy this file to my own laptop to work at home?” The client’s rule says no. Our rule says yes, if the laptop is encrypted. Nobody knows who to ask.
- 11. Team moves inWorks on client laptops and network
- 22. Client rules“Follow ours, you are on our site.”
- 33. Our rules“You are our staff, follow ours.”
- 44. Team guessesPicks the easier rule each time
- 55. ResultGaps in both rule books
Both sides are half right. The client is right that their network and their data are their responsibility, so their rules must apply to their things. Our security is right that these are our people, and our conduct rules, training and reporting go with them. What is missing is a short, written line between the two, and a named person who decides when they clash.
You will notice it when:
- The team asks “which rule applies?” and gets two answers.
- Someone keeps client files on their own laptop to avoid the client’s limits.
- The client’s security team and ours have never met.
- A small incident happens, and nobody knows who should report it, or to whom.
- The contract says “comply with client policies” but nobody has read those policies.
What exactly needs fixing
The first fix is not a new rule. It is one page that says which rules apply to what, and who decides. This card shows the whole problem on one page:
Nobody has said whose security rules apply to a team working inside a client.
Client laptops, client network, and our team’s daily habits.
A leak or a breach, and each side says the other’s rule applied.
- Data leak
- Blame game
- Confused team
- Contract breach
- 11. List both rule books
- 22. Agree who wins
- 33. Brief the team
Who fixes it: project head, both security teams
By when: before the team starts
A blank copy of this card is in the Tools section.
Why it happens
- Both rule books are real. Each side has good reasons for its own.
- The contract says little. Often only “comply with client policies”.
- Nobody compares the two before the team starts. The project begins in a hurry.
- The team is not security people. They want a simple answer, not a debate.
- The two security teams do not talk. Each assumes the other has it covered.
- Incidents have no clear route. So small problems are hidden or delayed.
What happens if you ignore it
The team picks the easier rule each time, and the gaps add up.
- Client data ends up on a laptop the client cannot protect.
- After an incident, each side says the other’s rule applied.
- The client sees our team as careless, and our own audit sees the client’s rules as ignored.
- The team loses trust in both security teams.
At a glance
| Question | Answer |
|---|---|
| How likely is it to hurt us? | Quite likely. Teams on client sites hit this in the first month. |
| Worst case? | Client data leaks from a device or habit that no rule covered. |
| What does it cost? | A breach clean-up, a client dispute, and a breach of contract. |
| What if we wait? | Habits form, and they are harder to change later. |
| What does the fix cost? | One page and one meeting before the team starts. |
How to fix it, step by step
Put both rule books side by side, once, and agree on the line between them.
- Get the client’s rules. Ask for the policies that apply to visiting teams. Read the parts that affect daily work.
- Put ours next to theirs. A simple two-column list: laptops, data copies, passwords, USB, remote work, reporting.
- Mark where they agree. Most rows will match. Say so, so the team stops worrying.
- Mark where they clash. For each clash, the stricter rule wins, unless both security teams agree otherwise in writing.
- Split by what the rule protects. The client’s things (laptops, network, data) follow the client’s rules. Our people’s conduct, training and incident reporting follow ours.
- Name one person who decides. When a case is not covered, the team has one name to ask, and one answer.
- Agree the incident route. Who reports, to whom, how fast, on both sides.
- Brief the team before day one. A 20-minute talk, and the one page on paper. Repeat it for new joiners.
The picture shows the split. The client’s things follow their rules, our people follow our conduct, and the stricter rule wins where they clash.
Who to bring in: The head of the project, security from our side, the client’s security contact, the client’s IT, and the team lead.
Tools and templates
Side-by-side rule list
| Topic | Client rule | Our rule | Which applies |
|---|---|---|---|
| Laptops | |||
| Copying data to other devices | |||
| Passwords and sign-in | |||
| USB and removable drives | |||
| Working from home | |||
| Reporting an incident |
Blank finding card
| Field | Write here |
|---|---|
| What is broken | One line, in plain words |
| Where it is | The system, team, or process |
| What could go wrong | In one sentence |
| What it costs us | Money, time, a leak, lost trust |
| The fix | The exact action |
| Who fixes it | One name or one team |
| By when | A date, not “soon” |
Email to the client’s security contact
Subject: Agreeing the rules before our team starts
Hi [name]. Before our team starts on your site, I would like to agree which security rules apply to what. I have put your policy and ours side by side. Most things match. For the few that do not, I suggest the stricter rule applies, and that you and I name one person each to decide. Could we meet for 30 minutes this week and sign off on one page?
Field tip
Do not ask the team to read two policy documents. Give them one page, with the answer to “Can I do this?” for the ten things they do every day.
Words used in this chapter
- Rule book: the set of security rules a company expects people to follow.
- Client site: working at the client’s office or on the client’s systems.
- Conduct: how people behave, such as how they handle data and passwords.
- Stricter rule: the rule that gives more protection when two rules clash.
- Incident route: who reports a problem, to whom, and how fast.