Operations | Monitoring | ITSM | DevOps | Cloud

In the first of these two articles, we covered the first five steps public sector organizations should take to change how they think about their cybersecurity to overcome this challenge. So far, we’ve explored: considering risk, tech environment knowledge, effective cyberhygiene, security at every level, and security as a trust-builder. We’ll continue by looking at the final five steps on this journey to build a stronger security strategy.

In our last post on Catchpoint’s 2020 CIO New Normal Survey we talked about how COVID-19 is driving a “reverse industrial revolution” that is fueling a mass exodus from America’s biggest (and most expensive) cities. This week, we focus on a more pragmatic set of findings: the IT lessons that we can learn from those American enterprises that have fared the best during the COVID-19 pandemic.

As a Customer Advocate, I talk to a lot of prospective Honeycomb users who want to understand how observability fits into their existing Site Reliability Engineering (SRE) practice. While I have enough of a familiarity with the discipline to get myself into trouble, I wanted to learn more about what SREs do in their day-to-day work so that I’d be better able to help them determine if Honeycomb is a good fit for their needs.

We recently announced the general availability of our Elasticsearch Service API. APIs help to automate tasks such as creating and scaling deployments, integrating with existing workflows, and testing. The Elasticsearch Service API supports the Open API Specification, which allows you to use tools like Swagger to generate software development kits (SDKs) in any programming language. You can import the API spec onto Postman and create a Postman Collection to create a test suite.

In a previous blog, we saw that the seemingly simple job of an Elasticsearch client — moving data between the calling code and the cluster — is actually quite complicated under the hood. Naturally, as much as we try to make the default behaviour of the client optimal for the majority of scenarios, there are situations where you want to configure, customize, or enable/disable certain features.

Subnetting isn’t hard but I often see even experienced network engineers looking for subnet calculators or trying to count in binary on their fingers. So how about a quick primer? To understand subnets, remember what a subnet is and think about the IP address in binary. A subnet is a range of IP addresses. All the devices in the same subnet can communicate directly with one another without going through any routers.

I recently spoke with Jeremy White who is using InfluxDB to monitor his aquariums. By collecting IoT sensor data, he has been able to better understand his 200 gallon salt-water aquarium full of fish and coral. The entire project can be found on GitHub. Caitlin: Tell us about yourself and your career. Jeremy: I’m a Senior Network Automation Consultant at Network to Code, and my background is in networking engineering. Network to Code is an industry leader in network automation.

Okay... and we’re back! Yes, there’s been a bit of a hiatus since you’ve heard from us in Core Security, but that’s not because we haven’t been busy. In fact, we’ve released a number of enhancements for both the security and user administration experiences of Splunk Enterprise. Going forward, we’ll be a bit more visible bringing you details on these enhancements.

Editor’s note: This post is a collaboration between Tim Tully, Splunk CTO, and Spiros Xanthos, Splunk’s vice president of product management for observability and IT Ops and previously the founder and CEO of Omnition. My love for the open-source software movement began with Linux in the ’90s and grew during my time at Yahoo! in the early days of Hadoop.

Raygun’s Launch Notes are your regular round-up of all the improvements we made to Raygun last month — from significant features to performance updates.