AI Isn't Creating Your Security Problems, It's Exposing Them: The Basics to Fix First
By LNS Engineer

AI Isn't Creating Your Security Problems, It's Exposing Them
Over the past couple of years, a new kind of security headline has become routine: an AI system finds a vulnerability that people missed. Sometimes it's in widely used open-source software. Sometimes it's a flaw that sat unnoticed for years.
It's easy to read those stories and conclude that AI has made the world less safe. We see it differently.
AI didn't put those weaknesses into your systems. They were already there. What has changed is how quickly and cheaply they can be found, by defenders and by attackers. Weak spots that used to stay hidden because nobody had time to look are now being surfaced at machine speed.
That's an uncomfortable message, but it's also a useful one. Most of what AI is exposing is old work businesses have been putting off. And that is something you can fix.
What AI-Driven Vulnerability Discovery Actually Looks Like
This isn't speculation. A few well-documented examples:
- Google's Big Sleep project. Google Project Zero and Google DeepMind reported that their AI agent found an exploitable memory-safety bug in SQLite, one of the most widely deployed database engines in the world, and that the bug was fixed before it appeared in an official release (Google Project Zero).
- AI-assisted fuzzing at scale. Google's security team reported that adding large language models to its OSS-Fuzz program helped uncover new vulnerabilities in open-source projects, including a flaw in OpenSSL that it says had likely been there for about two decades (Google Security Blog).
- DARPA's AI Cyber Challenge. The U.S. Defense Advanced Research Projects Agency ran a multi-year competition for AI systems that can automatically find and patch vulnerabilities in critical open-source code (AIxCC).
Notice the pattern. In every case, the vulnerability already existed. The AI simply found it faster. That same capability is available, in one form or another, to people with worse intentions.
The practical takeaway for a business in Cleveland, Akron, Canton, or Youngstown isn't "be afraid of AI." It's this: the time between "a weakness exists" and "someone finds it" is shrinking. Anything you've been deferring is now on a shorter clock.
The Real Issue: Security Debt
Most businesses we meet aren't careless. They're busy. A patch gets pushed to next month because the production line can't go down. An old server stays in service because one application depends on it. A firewall rule gets added for a vendor and never removed.
None of those decisions feels risky on its own. Added up over years, they become security debt. Like financial debt, it builds quietly, and it comes due at a bad time.
AI-driven discovery doesn't create that debt. It just shortens the time you have to pay it down.
Here are the deferred basics we see most often, roughly in the order we'd tackle them.
Priority 1: Know What You Actually Have
You can't patch, protect, or back up a device you don't know exists.
An accurate inventory of hardware and software is the first item in the CIS Critical Security Controls for exactly that reason (Center for Internet Security). Yet many small and mid-size businesses run on a spreadsheet that was last updated several IT people ago.
What typically turns up when we do a real inventory:
- A forgotten server in a closet still running a business application
- Network-attached storage or cameras exposed to the internet
- Personal devices on the main network
- Software nobody remembers installing, still running with old versions
Start here: build a current list of every device, operating system, and internet-facing service. Assign an owner to each one. Everything else on this list depends on it.
Priority 2: Close the MFA Gaps
Many businesses "have MFA." Far fewer have it everywhere it matters.
The common gaps we find are email accounts left out, admin accounts excluded "for convenience," remote access tools without it, and legacy sign-in methods that skip it entirely. Microsoft has reported that accounts using multi-factor authentication are more than 99.9% less likely to be compromised (Microsoft Security Blog). That protection only applies to the accounts actually covered.
Start here:
- Require MFA on email, remote access, VPN, cloud apps, and every administrator account
- Turn off legacy authentication that bypasses MFA
- Favor phishing-resistant methods (authenticator apps with number matching, or hardware keys) for privileged users
Priority 3: Work the Patch Backlog Strategically
A patch backlog can feel endless. The answer isn't to patch everything at once. It's to patch the right things first.
CISA maintains a Known Exploited Vulnerabilities catalog, a list of flaws that attackers are actively using in the real world (CISA KEV Catalog). That's a practical way to cut through the noise.
A sensible order:
- Internet-facing systems (firewalls, VPNs, remote access, web servers)
- Anything on the CISA KEV list
- Servers and systems holding sensitive data
- Workstations and laptops
Then set up a regular, scheduled patch cycle so the backlog doesn't come back. For manufacturers with production systems that can't easily go offline, this means planning maintenance windows rather than skipping updates indefinitely.
Priority 4: Change Defaults and Retire Shared Credentials
Default usernames and passwords on routers, switches, printers, cameras, and building systems remain one of the easiest ways into a network. CISA's Secure by Design initiative specifically calls on manufacturers to eliminate default passwords because they're so widely abused (CISA Secure by Design).
Until every vendor gets there, it falls to you.
Start here:
- Change every default admin password on network and connected devices
- Disable unused services and management interfaces
- Replace shared logins ("admin" used by five people) with individual accounts
- Store credentials in a proper password manager, not a spreadsheet
Priority 5: Face the End-of-Life Systems
Every business has one: the old machine running software nobody wants to touch.
The problem is simple. Once a product reaches end of support, the vendor stops releasing security fixes. Any flaw found after that date, by a person or an AI, stays open for good. Microsoft ended support for Windows 10 in October 2025, for example (Microsoft), and plenty of those machines are still in daily use.
Start here:
- Flag every system that's out of support or close to it
- Plan replacement or upgrade on a realistic timeline
- Where something truly can't be replaced yet (common with lab equipment, medical devices, and manufacturing controls), isolate it from the rest of the network and limit what can reach it
Priority 6: Segment the Flat Network and Review the Firewall
In a flat network, every device can talk to every other device. If one laptop is compromised, an attacker can reach the file server, the accounting system, and the backup appliance from the same spot.
Firewall rules have a similar problem. They pile up over the years. Rules added for a long-gone vendor or a one-time project stay open because nobody wants to break something by removing them.
Start here:
- Separate guest Wi-Fi, staff devices, servers, and specialized equipment into their own segments
- Keep backup systems and management interfaces on restricted networks
- Review every firewall rule: who requested it, why, and whether it's still needed
- Remove anything nobody can justify
This is especially important for healthcare organizations protecting patient data under HIPAA (HHS) and for higher ed campuses with many users and devices.
Priority 7: Prove Your Backups Actually Restore
We put this last on the list, but it's your safety net for everything above.
A backup job that reports "success" is not the same as a backup you can restore from. We regularly meet businesses whose backups have never once been restored as a test. Then a real incident happens and they learn the backups were incomplete, corrupted, or reachable by the same attacker.
Start here:
- Verify backups regularly, not only when you need them
- Run a real restore test of a critical system and time how long it takes
- Keep at least one copy isolated from your main network
- Write down a recovery playbook so the steps don't live in one person's head
Why Fragmented IT Makes These Basics Harder
Look back at that list. Asset inventory touches IT infrastructure. MFA and patching touch cybersecurity. Segmentation and firewall reviews touch network infrastructure. Restore testing touches backup and disaster recovery.
When each of those areas belongs to a different vendor, gaps open in the handoffs. The firewall provider assumes the IT provider handles patching. The backup vendor assumes the network team isolated the backup appliance. Everyone is doing their part, and the debt keeps growing in between.
That's why we built LNS around six pillars under one team and one SLA: WAN connectivity, cybersecurity, network infrastructure, IT infrastructure, UPS backup, and backup and disaster recovery. When one team owns the whole picture, the basics don't fall through the cracks between contracts.
A Calm, Honest Way Forward
We don't think the right response to AI-driven vulnerability discovery is panic. It's discipline.
The businesses that will be fine aren't the ones with the flashiest tools. They're the ones that know what they own, patch what matters, lock down accounts, retire what's outdated, segment what's sensitive, and know for certain that their backups work.
None of this is new advice. What's new is that the window for putting it off keeps getting shorter. Zero Gaps. Zero Excuses. isn't a slogan about perfection. It's about not leaving known weaknesses sitting there waiting to be found.
Let's Find Your Gaps Before Someone Else Does
We've spent more than ten years helping over 500 Northeast Ohio businesses, from manufacturers and healthcare practices to colleges, law firms, and financial services firms, move from reactive firefighting to proactive, monitored, verified IT.
If you're not sure where your own security debt sits, we'll help you find it and put it in a sensible order.
Schedule Your Consultation with our team today. Email us at [email protected] or call (216) 658-6988. We're local, we're independent, and we cover every pillar under one roof.
Related LNS Services
24/7 threat detection, ransomware protection, and incident response for your business.
Have IT Questions?
Our team is here to help. Schedule a free consultation and get answers from Northeast Ohio's IT experts.
Schedule Your ConsultationOr reach us directly
Free consultation. No obligation. No hard sell.