Datadog Integrates Cloud Infrastructure Monitoring with Cloud Foundry
Pivotal is a customer.
The Cloud: A Growing Driver for SD-WAN
A key driver for SD-WAN is that it can be used to intelligently optimize and secure connections to the cloud.
Wireless Troubleshooting: Lessons Learned
Peter Welcher reflects on what he learned while troubleshooting recent WLAN performance issues.
DevSecOps: 3 Things Infrastructure Pros Should Know
The DevOps movement has sometimes fallen short when it comes to security. DevSecOps hopes to change that.
5G Subscribers in North America Will Top 125M by 2022, Ericsson Report Says
SDN and NFV are necessary to make 5G use cases viable
First Speakers in Autumn Network Automation Course
Today I can tell you who the first speakers in the autumn 2017 network automation online course will be.
- Patrick Ogenstad (author of numerous open-source network automation modules and libraries) will talk about his journey to network automation, and lessons learned on the way.
- David Barroso will talk about his newest project: support of OpenConfig in NAPALM and Ansible (also discussed on a recent podcast).
Sounds promising? Why don’t you register before we run out of early-bird tickets?
More notes on US-CERTs IOCs
Yet another Russian attack against the power grid, and yet more bad IOCs from the DHS US-CERT.IOCs are "indicators of compromise", things you can look for in order to order to see if you, too, have been hacked by the same perpetrators. There are several types of IOCs, ranging from the highly specific to the uselessly generic.
A uselessly generic IOC would be like trying to identify bank robbers by the fact that their getaway car was "white" in color. It's worth documenting, so that if the police ever show up in a suspected cabin in the woods, they can note that there's a "white" car parked in front.
But if you work bank security, that doesn't mean you should be on the lookout for "white" cars. That would be silly.
This is what happens with US-CERT's IOCs. They list some potentially useful things, but they also list a lot of junk that waste's people's times, with little ability to distinguish between the useful and the useless.
An example: a few months ago was the GRIZZLEYBEAR report published by US-CERT. Among other things, it listed IP addresses used by hackers. There was no description which would be useful IP Continue reading
Security as an Enabler?
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:
- Bias toward action
- Forward Thinking
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
Ethernet Switch Market: Cisco Declines, Arista Gains
IDC first-quarter report shows competitors making headway in Cisco-dominated market.
Golang Magic: Package level vars, init
Magic
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.
Intro
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
Worth Reading: Keeping positive while job hunting
The post Worth Reading: Keeping positive while job hunting appeared first on rule 11 reader.