I have often wondered why the “security as an enabler” model is as unique as unicorns in the wild. I think the logic works in a vacuum and it would be great if it held true. However when humans and politics (layer 8 stuff) come into the mix, it seems that the cybersecurity team tend to be viewed as the naysayers that block progress. Quite honestly, the “security as an enabler” mantra only seems to work for those organizations that are directly profiting from the sale of cybersecurity. Those that understand the role cybersecurity plays in a typical organization realize that this is unfortunate.
With this thought in mind, I was reading through an article about the traits of CEO’s and found identified points that I think contribute to these challenges for information security:
By no means am I criticizing CEO’s for these traits—they are primary contributors to keeping a given business relevant in its industry. I’m just using these to help explain the fallacy of a “security as an enabler” mindset within a given organization.
CEO’s are the highest single point of authority within an organization. They often appoint CSO’s (Chief Security Officers) or CISO’s Continue reading
IDC first-quarter report shows competitors making headway in Cisco-dominated market.
Sometimes code appears to be magic. Layer up on layer of abstraction followed through with crazy names and advanced tricks. Great for the writer and a show case of knowledge, bad for readability and maintenance. This article explores removal of said magic by simplifying what packages can do.
I’m currently levelling up my learnings with Golang and keen to maintain the heat and make use of this skill. So, when Peter Bourgon posted this http://peter.bourgon.org/blog/2017/06/09/theory-of-modern-go.html, I took note. I’ve never met Peter, but I like what I read. In summary , his post is about removing the use of package level vars and the implicitly called init() function.
I am the first to admit to using package level vars and init. My first reaction to reading the article was being irked. Why irked? Because it’s easy to use package level vars and once you understand what init() is and when it’s called. Not using package level vars means you have to think about relationships and what needs to be passed what. Not using init() means you have to think about how something is instantiated and whether it’s unique and if it should be globally Continue reading
The post Worth Reading: Keeping positive while job hunting appeared first on rule 11 reader.
It configures desktop computers as nodes to support compute or storage functions.
“We use a nonblocking fabric…”
Probably not. Nonblocking is a word that is thrown around a lot, particularly in the world of spine and leaf fabric design—but, just like calling a Clos a spine and leaf, we tend to misuse the word nonblocking in ways that are unhelpful. Hence, it is time for a short explanation of the two concepts that might help clear up the confusion. To get there, we need a network—preferably a spine and leaf like the one shown below.
Based on the design of this fabric, is it nonblocking? It would certainly seem so at first blush. Assume every link is 10g, just to make the math easy, and ignore the ToR to server links, as these are not technically a part of the fabric itself. Assume the following four 10g flows are set up—
As there are four different paths between these four servers (B through E) and Z2, which serves as the ToR for A, all 40g of traffic can be delivered through the fabric without dropping or queuing a single packet (assuming, of Continue reading
Hypervisor platform uses containers to isolate hacks from spreading to critical car functions.
Carrier virtualization, programmability and the massive data sets from machine learning and analytics are driving new requirements for data centers.