The problem: 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 FS-02. It raises a ticket. IT closes it as “Done.” The next scan shows it is still open. Security reopens the ticket. IT feels doubted, and security feels ignored.
Words used here: a ticket is a written request for work, tracked in a system. A scan is an automatic check that looks for known weaknesses. Proof is something that shows the work was done, such as a screenshot or a re-scan result.
Think of a plumber who says “all fixed”
A plumber comes to fix a dripping tap, finishes quickly, packs the toolbox, and says, “All fixed!” The plumber leaves. Ten minutes later, the tap drips again. The plumber did work, and believes it is done. But nobody turned the tap on to check.
What it looks like at work
A weekly scan finds that Remote Desktop on file server FS-02 can be reached from the internet. Security raises a ticket: “Block Remote Desktop from the internet on FS-02.” An IT administrator adds a firewall rule the same day, and closes the ticket with the comment “Done, rule added.” The next scan shows Remote Desktop is still open. The rule was added in the wrong place, and a second path to the same server was not covered. Security reopens the ticket with a short note. IT replies, “I said it was done.”
- 11. Scan finds itRemote login is open to the web.
- 22. Ticket to ITGot it. I will block it today.
- 33. IT closes itDone. Rule added. Ticket closed.
- 44. Next scanStill open on server FS-02.
- 55. ReopenedI said it was done. You do not trust us.
Both sides are half right. IT is right that it did the work it was asked to do, and that it is busy with many tickets. Security is right that “done” must mean the weakness is gone, not that a change was made. What is missing is an agreed meaning of “done,” written in the ticket before the work starts, with proof, and a re-check that is a normal routine, not an accusation.
You will notice it when:
- Tickets are closed with one word: “Done.”
- The same finding appears in scan after scan.
- IT says “I already did that,” and security says “it is still open.”
- Nobody knows what “done” was supposed to prove.
- Messages between the two teams are getting shorter and sharper.
What exactly needs fixing
The first fix is not the server. It is the meaning of “done.” This card shows the whole problem on one page:
IT closed a ticket as done, but the next scan still shows remote login open on server FS-02.
File server FS-02 and the ticket between IT and security.
An attacker uses the open remote login to get in.
- Break-in risk
- Repeat tickets
- Lost trust
- Audit finding
- 11. Define done
- 22. Attach proof
- 33. Re-scan to close
Who fixes it: IT lead, security lead
By when: new rule in 2 weeks
A blank copy of this card is in the Tools section.
Why it happens
- “Done” means different things. To IT it means “I made the change.” To security it means “the weakness is gone.”
- Tickets are written as tasks, not outcomes. “Block it”, not “the scan must show it closed.”
- Closing is quick, checking is slow. And nobody is asked to check.
- There is more than one path. A rule on one door does not close the other doors.
- Checking feels like doubting. So nobody does it, until a scan does it for them.
- IT is measured on tickets closed. Not on weaknesses removed.
What happens if you ignore it
The weakness stays open while the ticket says it is closed. That is worse than an open ticket, because nobody is looking.
- An attacker uses the open remote login to get into the server.
- The same finding comes back in every scan and every audit.
- Trust between IT and security falls, and every ticket becomes an argument.
- An auditor sees a closed ticket and an open weakness, and asks who checks.
At a glance
| Question | Answer |
|---|---|
| How likely is it to hurt us? | Quite likely. Open remote login is one of the first things attackers try. |
| Worst case? | A break-in to a file server that the ticket system says is safe. |
| What does it cost? | A breach clean-up, a failed audit, and weeks of lost trust. |
| What if we wait? | The closed-but-open tickets pile up, and nobody knows which are real. |
| What does the fix cost? | One extra line in each ticket, and an automatic re-scan. |
How to fix it, step by step
Define “done” before the work, show proof when it is finished, and re-check as a routine.
- Write the outcome, not just the task. “Remote Desktop on FS-02 must not be reachable from the internet. The next scan must show it closed.”
- Put the proof in the ticket before the work starts. Name it: a screenshot of the firewall rule, and a re-scan result.
- IT does the work, and attaches the proof. The change, plus a screenshot. It takes two minutes.
- Security re-scans. It does not need to ask. An automatic re-scan a day later is enough.
- Close only when the re-scan is clean. Not when the ticket says “done.”
- If it is still open, say so, and say where. “Still reachable through the second path on port 3389.” Facts, not blame.
- Explain why the re-check exists. It is not about doubting IT. It is the same as a quality stamp on a product. Every ticket gets it.
- Look at the numbers once a month. How many tickets were reopened? If it is high, the problem is the meaning of “done,” not the people.
The picture shows the three parts. Each ticket gets all three, every time.
Who to bring in: The IT lead (who owns the work), the security lead (who owns the re-check), the person who runs the ticket system, and the managers of both teams.
Tools and templates
A ticket that says what done means (example)
| Field | Write here |
|---|---|
| What must be true | Remote Desktop on FS-02 is not reachable from the internet |
| How we will prove it | Screenshot of the rule, and a clean re-scan |
| Who does the work | One name in IT |
| Who re-checks | One name in security |
| Due date | A date, not “soon” |
| Closed when | The re-scan shows it closed |
Why a re-check is not an accusation (what to tell the team)
| Everyday example | The same idea at work |
|---|---|
| A pilot and co-pilot read the checklist aloud | Two people check, because anyone can miss something |
| A shop stamps “inspected” on a product | A scan stamps “closed” on a ticket |
| A plumber turns the tap on after the repair | A re-scan turns the door handle after the lock |
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 IT lead
Subject: A small change to how we close security tickets
Hi [name]. I know the team is busy, and I am not doubting your work. The Remote Desktop ticket on FS-02 was closed, but the scan still sees it open, probably through a second path. I would like us to agree what “done” means in each ticket before the work starts, with a screenshot as proof, and an automatic re-scan to close it. It should save us both reopened tickets. Could we try it on the next five tickets?
Field tip
Do not write “this was not fixed.” Write “the re-scan still sees it open through this path.” The first sounds like blame. The second is a fact.
Words used in this chapter
- Ticket: a written request for work, tracked in a system.
- Remote Desktop: a feature that lets someone log in to a computer from far away.
- Scan: an automatic check that looks for known weaknesses.
- Proof: something that shows the work was done, such as a screenshot or a clean re-scan.
- Re-scan: running the same check again after a fix, to see if the weakness is gone.