Worth Reading: New Strategies for Securing Our Personal Lives

I recently wrote an essay reflecting on the reality that nearly anyone with a life online is today subject to being hacked and having anything private become public. If the media is understandably going to publish newsworthy stuff, regardless of its provenance, and people are going to continue to use email and other communications that leave a record, what should be done? There are some tactical short term ways to mitigate risk. —Lawfare

The post Worth Reading: New Strategies for Securing Our Personal Lives appeared first on 'net work.

Worth Reading: Dyn’s DDoS Reveals IoT Weak Points

The massive internet outage last Friday that took out Twitter, GitHub, Spotify and others, was caused by a tsunami of incoming requests to Dyn, the DNS service provider supporting these companies. Where did all these requests pour in from? Hacked CCTV video cameras, digital video recorders and other IoT devices. The Internet of Things has arrived. And it brings huge security issues. —The New Stack

The post Worth Reading: Dyn’s DDoS Reveals IoT Weak Points appeared first on 'net work.

snaproute Go BGP Code Dive (13): Finding the tail of the update chain

Just in time for Hallo’ween, the lucky thirteenth post in the BGP code dive series. In this series, we’re working through the Snaproute Go implementation of BGP just to see how a production, open source BGP implementation really works. Along the way, we’re learning something about how larger, more complex projects are structured, and also something about the Go programming language. The entire series can be found on the series page.

In the last post in this series, we left off with our newly established peer just sitting there sending and receiving keepalives. But BGP peers are not designed just to exchange random traffic, they’re actually designed to exchange reachability and topology information about the network. BGP carries routing information in updated, which are actually complicated containers for a lot of different kinds of reachability information. In BGP, a reachable destination is called an NLRI, or Network Layer Reachability Information. Starting with this code dive, we’re going to look at how the snaproute BGP implementation processes updates, sorting out NLRIs, etc.

When you’re reading through code, whether looking for a better understanding of an implementation, a better understanding of a protocol, or even to figure out “what went wrong” on Continue reading

Worth Reading: The Internet Needs a Security Upgrade

The recent Internet outages caused by the DDoS attack on Dyn’s infrastructure highlights deep architectural issues that need resolution. Security and performance are intertwined, and both need fundamental upgrades. A few days ago I was working at a friend’s house. He likes to have Magic FM on during the day. They regurgitate the same playlist of inoffensive 70s, 80s and 90s pop music, with live drive-time shows. Later in the day I heard the DJ sputter how their Twitter access had gone wonky, so you couldn’t expect to interact with them via that channel. I thought little of it. —CircleID

The post Worth Reading: The Internet Needs a Security Upgrade appeared first on 'net work.

Worth Reading: Seven (more) deadly sins of microservices

It seems like the development community is quite excited about microservices these days, but at OSCON Europe, Daniel Bryant, who is chief scientist at OpenCredo, continued to point out some of the mistakes that architects and administrators routinely make while adopting to this new “Loosely coupled service oriented architecture with bounded contexts,” as Adrian Cockcroft described microservices. —The New Stack

The post Worth Reading: Seven (more) deadly sins of microservices appeared first on 'net work.

Wheel in the Tree

The post Wheel in the Tree appeared first on 'net work.

Worth Reading: The Facebook Wedge 100

Facebook is back in the news again. This time, it’s because of the release of their new Wedge 100 switch into the Open Compute Project (OCP). Wedge was already making headlines when Facebook announced it two years ago. A fast, open sourced 40Gig Top-of-Rack (ToR) switch was huge. Now, Facebook is letting everyone in on the fun of a faster Wedge that has been deployed into production at Facebook data centers as well as being offered for sale through Edgecore Networks, which is itself a division of Accton. Accton has been leading the way in the whitebox switching market and Wedge 100 may be one of the ways it climbs to the top. —The Networking Nerd

The post Worth Reading: The Facebook Wedge 100 appeared first on 'net work.

Worth Reading: Implementing multifactor authentication in the enterprise

IT systems must manage users and control access privileges to protect sensitive resources. This function is usually implemented in enterprise networks through authentication (verification of identity), authorization (control of access privileges) and accounting (recording of actions for auditing)—an “AAA” security framework. —Data Center Journal

The post Worth Reading: Implementing multifactor authentication in the enterprise appeared first on 'net work.

Reaction: Keith’s Law

Ethan pointed me to this post about complexity and incremental improvement in a slack message. There are some interesting things here, leading me in a number of different directions, that might be worth your reading time. The post begins with an explanation of what the author calls “Keith’s law”—

I am going to paraphrase the version he shared over lunch at the Facebook campus a few years ago and call it Keith’s Law: In a complex system, the cumulative effect of a large number of small optimizations is externally indistinguishable from a radical leap. If you want to do big things in a software-eaten world, it is absolutely crucial that you understand Keith’s Law. —Breaking Smart

The author attributes this to the property of emergence; given I don’t believe in blind emergence, I would attribute this effect to the combined intertwining of many intelligent actors producing an effect that at least many of them probably wanted (the improvement of the complex system), and each of them working in their own spheres to achieve that result without realizing the overall multiplier effect of their individual actions. If that was too long and complicated, perhaps this is shorter and better—

The law of Continue reading

Worth Reading: IoT devices and DDoS attacks

Embedded Internet-of-Thing (IoT) botnets are not a new phenomenon – we’ve seen them leveraged to launch DDoS attacks, send spam, engage in man-in-the-middle (MitM) credentials hijacking, and other malicious activities for several years. For example, a few years ago, a 75,000-strong botnet comprised of embedded devices – consumer broadband routers, in that instance – was found to be launching DDoS attacks. We routinely see IoT botnets comprised of webcams, DVRs, cable television set-top boxes, satellite set-top boxes, etc. used to launch DDoS attacks. —Arbor

The post Worth Reading: IoT devices and DDoS attacks appeared first on 'net work.

Worth Reading: The need for loud cyber weapons

In general, a tool used for offensive cyber operations involves a penetration mechanism and a payload. It’s often been observed that tools for exploitation (intelligence collection) and for attack (destruction or degradation) make use of the same techniques for penetration and differ primarily in payload (that is, in what is done to the target after penetration has been achieved). —Lawfare

The post Worth Reading: The need for loud cyber weapons appeared first on 'net work.

Biometric Password Protection

The post Biometric Password Protection appeared first on 'net work.

Worth Reading: The hidden world of news cameras

Most professional photographers are familiar with the fact that their cameras embed a wealth of metadata hidden in the images they create in formats like EXIF, IPTC and XMP. This metadata typically records the camera, lens and flash settings used to create the photograph, reflecting whether the image is a close-up macro portrait or a distant zoom lens shot. Yet, the fields can also contain textual descriptions of the image written by the photographer, authorship information, subject keywords, GPS coordinates, the names of public figures and events depicted in the image and a myriad other pieces of information that allow the image to be easily cataloged and searched. —Forbes

The post Worth Reading: The hidden world of news cameras appeared first on 'net work.

Worth Reading: IPv6 and the DNS

The exhortations about the Internet’s prolonged transition to version 6 of the Internet Protocol continue, although after some two decades the intensity of the rhetoric has faded and, possibly surprisingly, it has been replaced by action in some notable parts of the Internet. But how do we know there is action? How can we tell whether, and where, IPv6 is being deployed in today’s Internet? —Potaroo

The post Worth Reading: IPv6 and the DNS appeared first on 'net work.

Reaction: DevOps and Security

Over at TechBeacon, my friend Chris Romeo has an article up about DevOps and security. It’s interesting to me because this is actually an area I’d never thought about before, even though it makes sense. Given DevOps is essentially writing software to control infrastructure (like routers, compute, and storage), and software needs to be written in a way that is secure, then it should be obvious that DevOps software should be developed with good security principles gleaned from software development as part of the foundation.

And here we face a challenge, as Chris says—

There is no standard that defines security for DevOps, and the chances of a standard ever developing is small because different organizations are doing things their own way, and can’t even agree on a standard name. And while there is a standard for the secure development lifecycle (ISO/IEC 27034-1), few organizations are ever validated against it.

The key point in here is that every organization is doing things their own way. This isn’t wrong, of course, because every organization must have some “snowflakiness” to justify its existence, and that “snowflakiness” is often likely to show up, in a large way, in something like handling resources within Continue reading

Worth Reading: Microsoft and FPGAs

Microsoft’s embrace of programmable chips knowns as FPGAs is well documented. But in a paper released Monday the software and cloud company provided a look into how it has fundamentally changed the economics of delivering hardware as a service thanks to these once-specialty pieces of silicon. —The Next Platform

The post Worth Reading: Microsoft and FPGAs appeared first on 'net work.

Worth Reading: Some notes on today’s DDoS

As a techy, I want to know the composition of the traffic. Is it blindly overflowing incoming links with junk traffic? Or is it cleverly sending valid DNS requests, overloading the ability of servers to respond, and overflowing outgoing link (as responses are five times or more as big as requests). Such techy details and more make a big difference. Was Dyn the only target? Why were non-Dyn customers effected? —Errata Security

The post Worth Reading: Some notes on today’s DDoS appeared first on 'net work.

I2RS and Remote Triggered Black Holes

In our last post, we looked at how I2RS is useful for managing elephant flows on a data center fabric. In this post, I want to cover a use case for I2RS that is outside the data center, along the network edge—remote triggered black holes (RTBH). Rather than looking directly at the I2RS use case, however, it’s better to begin by looking at the process for creating, and triggering, RTBH using “plain” BGP. Assume we have the small network illustrated below—

In this network, we’d like to be able to trigger B and C to drop traffic sourced from 2001:db8:3e8:101::/64 inbound into our network (the cloudy part). To do this, we need a triggering router—we’ll use A—and some configuration on the two edge routers—B and C. We’ll assume B and C have up and running eBGP sessions to D and E, which are located in another AS. We’ll begin with the edge devices, as the configuration on these devices provides the setup for the trigger. On B and C, we must configure—

• Unicast RPF; loose mode is okay. With loose RPF enabled, any route sourced from an address that is pointing to a null destination in the routing table will Continue reading

Worth Reading: Hack Cameras, DVRs, and DDoS

A massive and sustained Internet attack that has caused outages and network congestion today for a large number of Web sites was launched with the help of hacked “Internet of Things” (IoT) devices, such as CCTV video cameras and digital video recorders, new data suggests. —Krebs on Security

The post Worth Reading: Hack Cameras, DVRs, and DDoS appeared first on 'net work.

Worth Reading: Facebook’s video views

The takeaway from Facebook’s bombshell that it had overstated a key measure of video ad viewership on its pages by about 80%: It’s not that the social-media giant “miscalculated” its numbers. It’s a fresh view into Facebook’s arrogance, both toward its advertisers and its nearly two billion users. Nothing’s new under the sun, of course — pride has goeth-ed before a fall for all of human history. And obviously does in the digital sphere, too: Facebook FB, +0.05% and its principal digital advertising rival, Google GOOG, +0.04% have been behaving as though customs and principles that have governed the advertising business for its entire history simply don’t apply to them. —Market Watch

The post Worth Reading: Facebook’s video views appeared first on 'net work.