KRACK Kills

Akins IT • October 17, 2017
Connect with us

KRACK has certainly been the topic on everybody’s mind in the last few days! The exploit has been coined as an “industry disrupter” and “effecting nearly everybody in the digital age.” It’s important to understand how this large scale wireless encryption exploit operates and how you can take preventative measures to protect your network from the KRACK exploit and future security compromises to come. 


The KRACK Vulnerability and What It Means for Your Network


Recently, a whitepaper was published that demonstrated a design flaw in the 4-way encryption handshake between access point and endpoint. WPA and WPA2, an otherwise ubiquitous wireless encryption standard was at the center of the exploit. Consequently, these standards are often the most utilized in larger corporate and enterprise networks where security is often leveraged as the highest priority. Given the large-scale use of WPA/2, it’s important to understand the implications of KRACK, how it will affect your network, and how to take steps for remediation and prevention.


About the KRACK Exploit


KRACK operates by leveraging security flaws in endpoints. Most commonly, this affects the endpoint (the device connecting to the wireless networks) and not the access point itself. The “attack” occurs during the 4-way handshake encryption phase before network traffic freely flows to the access point and throughout the network. Upon connecting, a client will begin a 4-way handshake to exchange encryption keys that will be verified for authenticity and eventually installed during phase 3 of the handshake and encrypt all subsequent data. Due to the nature of wireless connectivity, multiple retries may occur during this phase resulting in key resets. KRACK can leverage these resets by incorporating a “man in the middle attack” to force resets within this process and decrypt packets in the interim. During this period, client devices are essentially sending unencrypted data packets throughout the network and are susceptible to plaintext interpretation and visibility.


What Can I Do?


It’s important to note that this exploit targets a weakness of the endpoint’s execution of the 4-way handshake. In the majority of cases, the access point (regardless of vendor) is not susceptible to KRACK.


The quickest preventative solution is to immediately update your device to the latest firmware, as made available. Most vendors are scrambling to release fixes but many have already established roadmaps to upcoming firmware releases. Microsoft released a fix almost immediately. Apple will be releasing Mac OS and IOS fixes. Android and Linux updates are planned for the near future. 


AkinsIT Security Best Practices


We believe that a holistic security approach is ultimately the best solution to security vulnerability. As large wireless networks become more commonplace it’s important to follow these helpful guidelines at the minimum to ensure adequate protection.


  1. Always use a VPN. When a VPN is used, all data is encrypted from the endpoint. There are a wide variety of endpoint VPN solutions that can provide a comprehensive security solution. Exploits like KRACK become a non-issue when data is encrypted from the endpoint itself.
  2. Use caution when browsing. Spoofing and phishing sites are ubiquitous in today’s cyber landscape. Ensure that the page you are visiting is, indeed legitimate. Most sites that deal with privileged data use SSL to encrypt all access. You can verify this by viewing the SSL certificate typically found to the left of the web address within most browsers.
  3. Employ reputable Antivirus software. Running daily scans is crucial to ensure that your workstation is free of any viruses, trojans, or keyloggers that could track all of your data. A good AV solution will also take preventative measures to ensure that you are not stumbling upon “unwanted websites”
  4. Secure your network with an “NG” Firewall Solution. Many firewall vendors provide extra “NG” features like Intrusion Prevention, Antivirus, and Spam Filtering that can act as the last line of defense before ending and leaving your network. A good security solution begins at the firewall.


AkinsIT believes that good security is tantamount to a healthy and safe network. Let us help you evaluate your network and provide industry backed solutions to further strengthen your network and prevent exploits like KRACK from being an issue in the first place.

Download the Whitepaper
By Shawn Akins October 20, 2025
October 20, 2025 — Early today, Amazon Web Services experienced a major incident centered in its US‑EAST‑1 (N. Virginia) region. AWS reports the event began around 12:11 a.m. PT and tied back to DNS resolution affecting DynamoDB , with mitigation within a couple of hours and recovery continuing thereafter. As the outage rippled, popular services like Snapchat, Venmo, Ring, Roblox, Fortnite , and even some Amazon properties saw disruptions before recovering. If your apps or data are anchored to a single cloud, a morning like this can turn into a help‑desk fire drill. A multi‑cloud or cloud‑smart approach helps you ride through these moments with minimal end‑user impact. What happened (and why it matters) Single‑region fragility: US‑EAST‑1 is massive—and when it sneezes, the internet catches a cold. Incidents here have a history of wide blast radius. Shared dependencies: DNS issues to core services (like DynamoDB endpoints) can cascade across workloads that never directly “touch” that service. Multi‑cloud: practical resilience, not buzzwords For mid‑sized orgs, schools, and local government, multi‑cloud doesn’t have to mean “every app in every cloud.” It means thoughtful redundancy where it counts : Multi‑region or multi‑provider failover for critical apps Run active/standby across AWS and Azure (or another provider), or at least across two AWS regions with automated failover. Start with citizen‑facing portals, SIS/LMS access, emergency comms, and payment gateways. Portable platforms Use Kubernetes and containers, keep state externalized, and standardize infra with Terraform/Ansible so you can redeploy fast when a region (or a provider) wobbles. (Today’s DNS hiccup is exactly the kind of scenario this protects against.) Resilient data layers Replicate data asynchronously across clouds/regions; choose databases with cross‑region failover and test RPO/RTO quarterly. If you rely on a managed database tied to one region, design an escape hatch. Traffic and identity that float Use global traffic managers/DNS to shift users automatically; keep identity (MFA/SSO) highly available and not hard‑wired to a single provider’s control plane. Run the playbook Document health checks, automated cutover, and comms templates. Then practice —tabletops and live failovers. Many services today recovered within hours, but only teams with rehearsed playbooks avoided user‑visible downtime. The bottom line Cloud concentration risk is real. Outages will happen—what matters is whether your constituents, students, and staff feel it. A pragmatic multi‑cloud stance limits the blast radius and keeps your mission‑critical services online when one provider has a bad day. Need a resilience check? Akins IT can help you prioritize which systems should be multi‑cloud, design the right level of redundancy, and validate your failover plan—without overspending. Let’s start with a quick, 30‑minute review of your most critical services and RPO/RTO targets. (No slideware, just actionable next steps.)
By Shawn Akins October 13, 2025
How a Zero-Day in GoAnywhere MFT Sparked a Ransomware Wave—and What Mid-Sized IT Leaders Must Do Now
By Shawn Akins October 13, 2025
The clock is ticking: Learn your options for Windows 11 migration, Extended Security Updates, and cost‑smart strategies before support ends.
More Posts