The problems security teams really face, and how to handle them.
What CISSP, ISO 27001 and NIST don’t teach you. Each chapter explains one challenge in plain words, shows how it looks at work, and gives step-by-step actions, templates and a field tip.
Three Teams, One Problem, Nobody Fixing It
Security says, “This must be fixed.” IT says, “That is the project team’s system.” The project team says, “The client asked for it this way, and we…
Read the chapter →CHALLENGEHeld to Account, With No Power to Act
After an audit finding or an incident, leaders ask the head of security, “Why was this not fixed?” Security answers, “I asked IT and the project…
Read the chapter →CHALLENGEThe Security Ticket That Never Makes the Sprint
Security opens a ticket for a serious weakness. The product owner says the sprint is full of client features, and the ticket has no business value…
Read the chapter →CHALLENGEThe Scanner That Breaks the Build
Security adds a code scanner to the build. On day one it fails builds because of hundreds of old problems and false alarms. Developers say, “The…
Read the chapter →CHALLENGEOne Shared Password and Real Customer Data in Test
Developers share one admin password and copy real customer data into test systems, because it is quick. Security says it is a risk and a failed…
Read the chapter →CHALLENGEThe Client Insists on the Old TLS 1.0 Connection
Your client’s old billing system can only connect to ours using TLS 1.0, an old way of locking the connection that attackers can now break. Your own…
Read the chapter →CHALLENGEA Needed Fix That Is Not in the Contract
In the middle of a project, a security fix turns out to be needed. It is not in the contract, and the project has no people or money left for it. The…
Read the chapter →CHALLENGEAsked to Protect Everything, With No Money of Its Own
Security is expected to keep the company safe, but it has no budget of its own. Each tool, each person, and each fix has to be asked for, one team at…
Read the chapter →CHALLENGEInvited in the Last Week
Security hears about a project when it is almost finished. It is asked to “just sign off.” When it finds a big problem, the project team says, “It is…
Read the chapter →CHALLENGETwo Rule Books, One Team
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…
Read the chapter →CHALLENGEThe Change Request Nobody Wants to Raise
A security fix needs a change request to the client. The delivery manager will not raise it, for fear of upsetting the client or looking like the…
Read the chapter →CHALLENGEPaid for the Date, Not for the Fix
The delivery manager is judged on dates and profit. A security fix costs both, so it feels like a threat to their own results, and they say, “Let us…
Read the chapter →CHALLENGEThe Weakness Between the Server and the App
A server is run by IT. The application on it is run by a project team. A security scan finds a weakness, and it is not clear who should fix it. IT…
Read the chapter →CHALLENGEThe Cloud Storage IT Never Heard About
A project team is under pressure to hit a client demo date. IT says new file storage takes three weeks. The team creates its own cloud storage on a…
Read the chapter →CHALLENGEClosed as Done, But Still Open
Security finds that Remote Desktop, the feature that lets someone log in to a server from far away, is open to the internet on a file server called…
Read the chapter →CHALLENGEBought, But Nobody Has Time to Install It
Security buys a tool that watches every laptop for attacks. It is a small program, called an agent, that must be installed on each of the 500…
Read the chapter →CHALLENGE“You Run the Servers, So You Patch Them”
Security wants all 120 servers patched every month. A patch is a small update that closes a known weakness. Security says, “You run the servers, so…
Read the chapter →CHALLENGEDevelopers Need Admin Rights, and Get Two Answers
A team of 25 developers needs administrator rights on their laptops to install Docker Desktop and a database tool. IT says, “No admin rights for…
Read the chapter →CHALLENGESecurity Sign-Off Is Asked For, but Given Two Days at the End
A client contract says the system needs a security sign-off before go-live. The project team builds for three months and then asks security to sign…
Read the chapter →CHALLENGETwo Security Teams, One Audit Finding, No Owner
In an internal audit, risk and compliance says, “That is technical, so it is not our job.” Security operations says, “Checking controls is audit…
Read the chapter →CHALLENGEThe Partner Nobody Agreed On
The IT team and the security team want different partners to install a new security tool. One side wins the vote. When the work hits trouble, the…
Read the chapter →CHALLENGEA Policy the Security Team Cannot Follow
Risk and compliance writes a new alert policy: “Every alert must be closed within 15 minutes.” The security operations team (the SOC) gets about 300…
Read the chapter →CHALLENGEThe Setting Change That Broke the Audit Proof
The security operations team (the SOC) is running out of disk space on the firewall log server. An engineer changes the setting from keeping logs for…
Read the chapter →CHALLENGEEvery Quarter the Evidence Request Lands in the Wrong Week
Four times a year, risk and compliance emails the security operations team (the SOC): “Please send the list of alerts you handled this quarter, by…
Read the chapter →CHALLENGETwo Answers From the Same Security Team
A project is building a customer portal. The security architect writes: “Use the company login system, with a second step.” The same day the…
Read the chapter →CHALLENGEThree Numbers for One Board Slide
The CISO builds the quarterly board report from numbers sent by three sub-teams. The slide says “critical vulnerabilities.” The vulnerability team…
Read the chapter →CHALLENGEThe CISO Who Reports to the CIO
The CISO (head of security) reports to the CIO (head of IT). A penetration test finds that a group of old servers, owned by the CIO’s own team, are…
Read the chapter →CHALLENGEThe New CISO’s First 90 Days
A new CISO joins a company. On day one she finds three half-finished programs: a project to add a second sign-in step for everyone, a project to list…
Read the chapter →CHALLENGEThe Risk Scored Low While the SOC Sees Attacks
The risk team scores the customer payment API as Low. The score comes from a yearly review, done in the calm of a workshop. Meanwhile the security…
Read the chapter →CHALLENGEThe “Yes” That Operations Knows Is Only Partly True
A large client sends a security questionnaire before signing a contract. One question asks: “Is a second sign-in step required for all staff?” The…
Read the chapter →CHALLENGEAfter the Incident, Both Teams Blame Each Other
The security operations team (the SOC) finds customer data exposed on the internet and mentions it in a team chat. Two days later, by chance, the…
Read the chapter →CHALLENGERequests Go to Whoever People Know
A developer wants to use a new file-sharing tool for a project. There is no place to ask security, so he messages Sam, an engineer he knows. Sam is…
Read the chapter →CHALLENGEThe Tool Picked Through a Vendor Friend
The head of IT has dinner with a salesperson he has known for years. The salesperson describes a new email security gateway, and the price is good…
Read the chapter →CHALLENGETwo Leaders Back Two Different Tools
The company needs to replace its endpoint protection (the software that guards laptops and servers). The head of IT backs Tool A, which is cheaper…
Read the chapter →CHALLENGEThe Cheapest Bid Wins and the Security Line Drops Off
A business team needs a new backup service. Security writes two must-haves: backups must be encrypted, and the data must stay in the European Union…
Read the chapter →CHALLENGEThe Partner Finishes and Leaves, Half Set Up
A company hires an implementation partner (an outside firm that sets up a product for you) to add a second sign-in step, such as a code on a phone…
Read the chapter →CHALLENGEThe Demo Promised More Than the Product Does
A vendor shows the security team a smooth demo. Alerts from the monitoring tool open tickets in the help desk system on their own, and the head of…
Read the chapter →CHALLENGEThe Friendly Partner Who Keeps Getting the Work
For six years, the company has used the same integrator (an outside firm that connects and sets up systems) for its security projects. The people are…
Read the chapter →CHALLENGEThe Partner Who Kept Full Admin for Three Years
To speed up a rollout, the IT admin gives the implementation partner a login with full administrator rights, meaning the right to change anything in…
Read the chapter →CHALLENGEThe New Security Tool That Overlaps One IT Already Owns
The CISO buys a vulnerability scanner (a tool that checks servers for known weaknesses) to scan about 300 servers each night. IT already pays for a…
Read the chapter →CHALLENGEThe Trial That Never Ended and Became Production
A team lead signs up for a 30-day free trial of a file-sharing tool, to share large files with customers. Nobody in security or IT is told. The…
Read the chapter →