Machine learning has infiltrated the world of security tooling over the last five years. That’s part of a broader shift in the overall software market, where seemingly every product is claiming to have some level of machine learning. You almost have to if you want your product to be considered a modern software solution. This is particularly true in the security industry, where snake oil salesmen are very pervasive and vendors typically aren’t asked to vigorously defend their claims.

Australia’s government has big aspirations to increase public service capability and capacity. By reducing its reliance on external firms and bringing capabilities in-house, the government hopes to boost efficiency, improve spending, and become a more equitable, inclusive employer. This transition won’t necessarily be easy. Manual processes and disparate legacy systems will make it difficult for government agencies to deliver great employee experiences.

“Automation” and “orchestration” are terms that frequently appear within the same sentence – which is unsurprising, because they are closely related. In fact, they’re so similar in meaning that it can be easy to confuse their meanings or assume that there is basically no real difference between security automation and orchestration. But, as with many concepts in the world of IT and security (“observability” vs.

Developers are building features at an unprecedented speed using what they need from the software ecosystem. These ever-expanding options include open-source libraries and packages, SaaS tools, deployment systems, cloud services, and more. To keep things secure, we always need the same thing: a secret.