We have to get everyone back to work. The global restart of economies derailed by the coronavirus pandemic is challenging organizations across the board. And from one industry to the next, IT must be a central player in establishing a new normal. Organizations that had to entirely shut down facilities — retail stores, manufacturing plants, restaurants, theme parks — may particularly struggle to reestablish operations with new approaches that protect worker and customer health.

Got multiple AWS data sources in the same S3 bucket but struggle with efficient SNS notifications based on prefix wildcards? Well, struggle no more, we’ve got your back. Many of our customers have a centralised S3 Bucket for log collection for multiple sources and accounts. For example, all Config, CloudTrail and Access Log logs may be routed into one central bucket for an organisation.

A growing attack surface and the exponential rise of data has opened the floodgates for breaches, leading to increased scrutiny by regulatory agencies. It’s not surprising that in recent years, regulators have had to double down with compliance mandates that are more stringent and punitive than ever before.

So I've only been at Splunk for 8 months, and in the short amount of time I've been here, one of the most common questions I've been asked is “How do I get an alert when Splunk is not receiving logs?". As a matter of fact, if I had $0.05 each time I was asked this question, I would have $0.25! Surprisingly, with this being such an often-asked question, I haven't been able to find much documentation on how to accomplish this using the native features of Splunk.

Is it the middle of Spring already? (And Fall, for our Southern Hemisphere readers!) A lot has happened at Splunk since our last developer updates at .conf19. In case you missed any of the great developer sessions there, grab some time to watch what you missed!

In May 2019, Bloomberg Government reported that Federal agencies planned to move 272 information technology programs to the cloud in FY2020. Fast forward to April 2020 — they reported that there are more than 1,800 federal IT programs that are either migrating or considering migrating to the cloud in fiscal 2021, signifying a rapid increase in cloud adoption in the federal government. How might COVID-19 affect this explosive increase in cloud interest?

At Splunk, we're listening to our customers and offering more predictable, flexible, and familiar pricing options as part of our Data-to-Everything Pricing model. In particular, Splunk’s new infrastructure pricing metric changes the paradigm of how much data you can analyze with Splunk, allowing users to move toward a value-driven pricing model that better aligns what you pay with real value you can extract from using Splunk products.

When we discuss Splunk Phantom with customers here at Splunk, we end up talking about phishing pretty frequently. As discussed in a recent blog post, "Phishing Emails — Don’t Get Reeled In!," phishing is a super common issue that almost everyone deals with ad nauseum. It’s also a nuisance to investigate. The good news is that automation excels at dealing with repetitive, mind-numbing workflows like phishing investigations.

Data is the lifeblood of any organisation. It’s what drives customer engagement, boosts employee productivity, streamlines operations and, in some cases, even transforms age-old companies into digital powerhouses.

IDG’s recent “State of the CIO” survey across IT leaders has revealed the impact of COVID-19 on IT organizations and the sudden and unforeseen shifts of their initial 2020 plans.