A zero-day is not magic. It is a flaw attackers can use before the maker has released a fix. The name means the maker has had zero days to respond.
While there is no fix, you do other things: turn off the risky feature, put a lock in front of it, watch for strange activity, and update the moment a fix arrives.
Practical steps: make people sign in before they can reach it, limit who can reach it, switch off the part that is broken, and keep a closer eye on it.
The less an attacker can reach from one way in, the less a surprise flaw costs you. That idea is called blast radius, and it is the next lesson.
Words you will see
- Zero-day
- A flaw attackers can use before the maker has released a fix.
- Workaround
- A temporary step that reduces risk until a real fix is available.
- Mitigation
- Any step that makes an attack less likely or less harmful.
Decision
The maker of an app says attackers are already using a flaw. There is no fix yet, but there is a workaround. What is the best move?
What to do instead
- Follow the maker's own announcement, not rumours on social media.
- Limit who and what can reach the affected thing.
- Decide ahead of time who can approve an emergency change.
Common mistakes
- Waiting passively for the patch.
- Applying random fixes from social media instead of the vendor's guidance.
- Forgetting to update again once the real patch is released.
References and further reading
- CISA Known Exploited Vulnerabilities catalogCISA
- NCSC: Incident managementUK National Cyber Security Centre
Finished this one?
Add it to What I learned and earn 50 Trust. You can open your list from the badge at the bottom of the page.