Security Blog
The latest news and insights from Google on security and safety on the Internet
802.11s Security and Google Wifi
7. února 2017
Posted by Paul Devitt, Security Engineer
Making sure your home network and information stay secure is our top priority. So when we launched the Google OnHub home router in 2015, we made sure
security was baked into its core
. In 2016 we took all we learned from OnHub and made it even better by adding mesh support with the introduction of
Google Wifi
.
Secure to the core - Always
The primary mechanism to making sure your Wifi points stay safe is our verified boot mechanism. The operating system and code that your OnHub and Google Wifi run are guaranteed to have been signed by Google. Both OnHub and Google Wifi use
Coreboot and Depthcharge
from ChromeOS and ensure system integrity by implementing
DM-Verity
from Android. To secure Userspace, we use process isolation with
Seccomp-BPF
and a strict set of policies.
On the software side, Google Wifi and OnHub are subject to
expansive fuzz testing
of major components and functions. The continual improvements found by fuzzing are fed into Google Wifi and OnHub, and are made available through the regular automatic updates, secured by Google’s cloud.
802.11s Security for WiFi
In 2016 with the launch of Google Wifi, we introduced
802.11s mesh technology
to the home router space. The result is a system where multiple Wifi Points work together to create blanket coverage. The specification for 802.11s recommends that appropriate security steps be taken, but doesn’t strictly define them for people to use. We spent significant time in building a security model into our implementation of 802.11s that Google WiFi and OnHub could use so that your network is always comprised of exactly the devices you expect.
As each mesh node within the network will need to speak securely to its neighboring nodes, it's imperative that a secure method, which is isolated from the user, is established to form those links. Each Wifi node establishes a separate encrypted channel with its neighbors and the primary node. On any major network topology change (such as a node being factory reset, a node added, or an event where an unexpected node joins the network), the mesh will undergo a complete cycling of the encryption keys. Each node will establish and test a new set of keys with its respective neighbors, verify that it has network connectivity and then the network as a whole will transition to the new keys.
These mesh encryption keys are generated locally on your devices and are never transmitted outside of your local network. In the event that a key has been discovered outside of your local network, a rekeying operation will be triggered. The rekeying operations allow for the mesh network to be fully flexible to the user’s desire and maintain a high level of security for devices communicating across it.
Committed to security
We have an ongoing commitment to the security of Google Wifi and OnHub. Both devices participate in the
Google Vulnerability Rewards Program (VRP)
and eligible bugs can be rewarded up to $20,000 (U.S). We’re always looking to raise the bar to help our users be secure online.
Žádné komentáře :
Okomentovat
Štítky
#sharethemicincyber
#supplychain #security #opensource
AI Security
android
android security
android tr
app security
big data
biometrics
blackhat
C++
connected devices
CTF
diversity
encryption
federated learning
fuzzing
Gboard
google play
google play protect
hacking
chrome
chrome enterprise
chrome security
interoperability
iot security
kubernetes
linux kernel
memory safety
Open Source
pha family highlights
pixel
privacy
private compute core
Rowhammer
rust
Security
security rewards program
sigstore
spyware
supply chain
targeted spyware
tensor
Titan M2
VDP
vulnerabilities
workshop
Archive
2026
dub
bře
úno
led
2025
pro
lis
říj
zář
srp
čvc
čvn
kvě
dub
bře
úno
led
2024
pro
lis
říj
zář
srp
čvc
čvn
kvě
dub
bře
úno
led
2023
pro
lis
říj
zář
srp
čvc
čvn
kvě
dub
bře
úno
led
2022
pro
lis
říj
zář
srp
čvc
čvn
kvě
dub
bře
úno
led
2021
pro
lis
říj
zář
srp
čvc
čvn
kvě
dub
bře
úno
led
2020
pro
lis
říj
zář
srp
čvc
čvn
kvě
dub
bře
úno
led
2019
pro
lis
říj
zář
srp
čvc
čvn
kvě
dub
bře
úno
led
2018
pro
lis
říj
zář
srp
čvc
čvn
kvě
dub
bře
úno
led
2017
pro
lis
říj
zář
čvc
čvn
kvě
dub
bře
úno
led
2016
pro
lis
říj
zář
srp
čvc
čvn
kvě
dub
bře
úno
led
2015
pro
lis
říj
zář
srp
čvc
čvn
kvě
dub
bře
úno
led
2014
pro
lis
říj
zář
srp
čvc
čvn
dub
bře
úno
led
2013
pro
lis
říj
srp
čvn
kvě
dub
bře
úno
led
2012
pro
zář
srp
čvn
kvě
dub
bře
úno
led
2011
pro
lis
říj
zář
srp
čvc
čvn
kvě
dub
bře
úno
2010
lis
říj
zář
srp
čvc
kvě
dub
bře
2009
lis
říj
srp
čvc
čvn
bře
2008
pro
lis
říj
srp
čvc
kvě
úno
2007
lis
říj
zář
čvc
čvn
kvě
Feed
Follow @google
Follow
Give us feedback in our
Product Forums
.
Žádné komentáře :
Okomentovat