Last Friday, October 21, a lot of people on the East Coast woke up to find that big parts of the internet weren't working. Twitter, Netflix, Reddit, Spotify, GitHub, PayPal, and plenty of others were unreachable or painfully slow, in waves that stretched through the day. None of those companies had actually been hacked. Something they all depended on was being flooded.
The target was Dyn, a company that provides DNS services to many of the internet's biggest sites. The weapon, according to Dyn and security researchers, was largely a botnet called Mirai, built out of everyday internet-connected gadgets: security cameras, digital video recorders, and similar devices, many still running the username and password they shipped with. It's quite possible some of them were sitting in small offices just like yours.
What DNS is, and why hitting it works
DNS is the internet's phone book. When you type a website name into your browser, your computer asks a DNS server to translate that name into the numeric address where the site actually lives. Companies like Dyn run those lookups for thousands of websites.
A DDoS (distributed denial of service) attack floods a target with so much junk traffic from so many sources that it can't answer legitimate requests. Overwhelm the DNS provider, and browsers can't find the sites that depend on it, even though the sites themselves are running fine. That's why so many unrelated services went down at once.
How Mirai builds its army
Mirai is remarkably simple. It scans the internet for devices that allow remote login, then tries a short list of common factory default usernames and passwords, the kind printed in the manual: admin/admin, root/12345, and so on. When one works, the device is infected and joins the botnet, ready to send traffic wherever it's told.
The source code for Mirai was posted publicly online at the end of September, shortly after it was used in record-breaking attacks against security journalist Brian Krebs's website and a French hosting provider. Once code like that is public, anyone can run their own version, and more attacks are almost certain.
The devices that took down Twitter weren't hacked with anything clever. Someone just tried the password from the manual.
Why this is a small business problem
Walk through a typical small office and count the devices that connect to the internet without anyone thinking of them as computers. Security cameras and the DVR or NVR that records them. The alarm panel. A network-attached storage box. The thermostat. The conference room TV. Printers. Many of these were installed by a vendor who set them up to be viewable from a phone app, and never changed the login.
If one of your devices is part of a botnet, it's using your internet connection to attack other people. You might notice slower internet, or you might notice nothing at all. Worse, a compromised device is sitting inside your network, where it could potentially be used as a foothold to reach your computers and data. And a hacked security camera is, well, someone else watching your office.
How to secure your cameras and other devices
Change default passwords
This is the big one. Every device that has a login should have a unique, strong password, not the factory default. That includes the DVR, each camera if they have their own logins, the router, and the Wi-Fi access points. Be aware that some devices affected by Mirai have hard-coded credentials for remote services like Telnet that can't be changed through the normal settings. For those, the next steps matter even more.
Keep them off the open internet
Many camera systems are set up with port forwarding on the router so they can be viewed remotely. That exposes the device's login directly to anyone scanning the internet. Better options:
- Use a VPN to connect to the office, then view cameras as if you were on site.
- Use the manufacturer's cloud viewing service only if it's reputable and keeps the device itself unexposed.
- Turn off Universal Plug and Play (UPnP) on your router, which lets devices open holes in your firewall on their own.
- Review your router's port forwarding rules and remove anything you don't recognize or no longer need.
Update the firmware
Device makers do release fixes. Check the manufacturer's website for firmware updates for your cameras, DVR, and router, and install them. If a device is so old it no longer gets updates, it's time to plan a replacement. Some manufacturers have already announced recalls or fixes for devices tied to Mirai.
Separate them from your business network
Cameras and gadgets don't need to sit on the same network as your accounting PC. A separate network segment or VLAN for cameras and smart devices limits what a compromised device can reach.
Buy with security in mind
When you're shopping for cameras or other connected devices, ask the installer: Does it force a password change at setup? Does the manufacturer release security updates? Can it be viewed remotely without opening ports? Cheapest isn't always a bargain.
Your IoT checklist for this week
- Make a list of every internet-connected device in the office, not just computers.
- Change every default password you find.
- Check your router for port forwarding and UPnP, and close what you don't need.
- Look up firmware updates for cameras, DVRs, and your router.
- Move cameras and smart devices onto their own network segment.
- Ask your camera or alarm installer how remote access is configured.
- Replace devices that can't be updated or secured.
The bottom line
Friday's outage was a reminder that the internet is only as strong as its weakest connected device, and a lot of those devices are cheap cameras with factory passwords. You can't fix the whole internet, but you can make sure nothing in your office is helping to break it. If you'd like help auditing the devices on your network and locking them down, our cybersecurity services cover exactly that. Reach us at info@pinellasit.com.
