Author Archives: Russ
Author Archives: Russ
The post Worth Reading: A better way to compare yourself appeared first on rule 11 reader.
The post Worth Reading: Who pays security costs? appeared first on rule 11 reader.
A good bit has been written about the recent WannaCry outbreak over the last few weeks; rather than stringing the best out through Worth Reading posts, I have collected the three best posts on the topic here.
Over the weekend a cyber attack known as “WannaCry” infected hundreds of computers all over the world with ransomware (malware which encrypts your data until you pay a ransom, usually in Bitcoin). The attack takes advantage of an exploit for Windows known as “EternalBlue” which was in the possession of NSA and, in mid April, was made public by a group known as “The Shadow Brokers.” Microsoft issued a patch for the vulnerability on March 14 for all supported versions of Windows (Vista and Continue reading
The post Worth Reading: The Embiggening Bite of GPUs appeared first on rule 11 reader.
The post Worth Reading: Key logger audio driver appeared first on rule 11 reader.
There has been a lot of chatter recently in the 5G wireless world about network slices. A draft was recently published in the IETF on network slices—draft-gdmb-netslices-intro-and-ps-02. But what, precisely, is a network slice?
Perhaps it is better to begin with a concept most network engineers already know (and love)—a virtual topology. A virtual topology is a set of links, with some subset of connected devices (either virtual or real), that act as a subset of the network. Isn’t such a subset of the network a “slice” if you look at it from a different angle? To ask the question in a different way: how are network slices different from virtual network overlays?
To begin, consider the control plane. In the world of virtual topologies, there is generally one control plane that provides reachability, as well as sorting reachability into each virtual topology. For instance, BGP carries a route target and a route discriminator to indicate which virtual topology any particular destination belongs to. A network slice, by contrast, actually has multiple control planes—one for each slice. There will still be one “supervisor control plane,” of course, much like there is a hypervisor that manages the resources of each Continue reading
The post Worth Reading: Mapping with wifi appeared first on rule 11 reader.
Just like organizations can build up technical debt, so too can they also build up something called “security debt,” if they don’t plan accordingly… In the past, security used to be ignored by pretty much everyone, except banks. But security is more critical than it has ever been because there are so many access points. We’ve entered the era of Internet of Things, where thieves can just hack your fridge to see that you’re not home.
The post Worth Reading: Security debt appeared first on rule 11 reader.
This is the blog post by Ivan I discuss in the video, and this is an older post here on Rule11 about the same topic, if you prefer your explanations written.
The post Microloops Explained (in video) appeared first on rule 11 reader.
The post Worth Reading: Hype to reality appeared first on rule 11 reader.
Introspection can be lethal for a writer. Then again, so can water if you drink too much. If you can moderate your intake, it sustains you. —Arc
The post Worth Reading: The introspective Ouroborus appeared first on rule 11 reader.
The post Worth Reading: Humans training their AI replacements appeared first on rule 11 reader.
The post Worth Reading: Bartering for privacy appeared first on rule 11 reader.
The post On the ‘net: A New Routing Stack Comes to Town appeared first on rule 11 reader.
The post Worth Reading: Openstack and complexity appeared first on rule 11 reader.
The post Worth Reading: RDNSS enabled in Windows 10 appeared first on rule 11 reader.
The biggest problem with IoT security is that most devices are going to be relatively simple and inexpensive connected things. The bandwidth consumption of these devices should be kept to the minimum to save bandwidth. Yet at the same time, security is supposed to be a continuous process. This involves a party that is responsible for keeping an eye on the various security vulnerabilities that emerge from time to time, and another one to make sure that suitable patches are being prepared and applied on timely basis. —CircleID
The post Worth Reading: IoT devices will never be secure appeared first on rule 11 reader.