Routers are a perfect target for attack both because of the important role they play and the generally insecure way they are configured. For example, a large reason (perhaps the major reason) that IoT security is such an issue is that the routers fronting IoT devices often fail to protect them behind a firewall. (Yes, I’m talking UPnP.) A hacked router is a disaster: it may participate in a botnet, spy on you, steal your passwords, push malware to your devices, or bombarded you with ads.
Michael Horowitz offers an overview of some of the more interesting and widespread router flaws from the last few years. He then shares configuration tips on how to make any router as secure as possible and suggestions on testing an existing router. You’ll learn why you should know your DNS and what to look for when buying a new router. Michael ends with a look at the security of the newer mesh router systems.
Michael Horowitz is an independent computer consultant and blogger who works with small businesses and the self-employed, working on everything from websites, networks, software upgrades, backup strategies, and data recovery to tutoring and purchasing advice. Michael wrote his first computer program in 1973 and has been a computer nerd ever since. Previously, he spent more than 20 years working in an IBM mainframe (MVS) environment—developing applications in COBOL, Assembly Language, VSAM, CICS, and the ever-present batch environment; working with the IDMS database; and working with DB2 for MVS as a database administrator. He also worked in the Research and Development Group of a large Wall Street financial company and did some technical writing, producing manuals and the like for a mainframe software company. Michael holds a degree from New York University, where he minored in both computer science and mathematics.
©2017, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • email@example.com