The Australian Signals Directorate (ASD) has quietly published its process for deciding when knowledge of cybersecurity vulnerabilities is kept secret.
This is the first official acknowledgement that the ASD might not disclose all of the vulnerabilities it discovers. However, knowledge of secret vulnerabilities would have always been an essential part the agency’s toolkit for offensive cyber operations.
The document Responsible Release Principles for Cyber Security Vulnerabilities was posted on the ASD’s website on Friday.
The policy stresses that the agency’s starting position for when it finds a weakness is to disclose it and work with vendors to ensure that patches are available before it is made public.
“Occasionally, however, a security weakness will present a novel opportunity to obtain foreign intelligence that will help protect Australians. In these circumstances, the national interest might be better served by not disclosing the vulnerability,” the policy reads.
“The decision to retain a vulnerability is never taken lightly. It is only made after a careful multi-stage expert analysis, and is subject to rigorous review and oversight.”
Also: Cyber blitzkrieg replaces cyber Pearl Harbor
ZDNet understands this isn’t a new decision-making framework, but one that has been in operation in various forms for quite some time. It’s being made public as part of ASD director-general Mike Burgess’ strategy to bring the agency “out from the shadows” and to dispel the notion that it warehouses large numbers of zero-day exploits.
The key decision-making principle is that the national interest to keep a vulnerability secret must strongly outweigh the national interest of disclosing it, based on the existence of a “critical intelligence requirement”.
“This might happen if the weakness allows us to gather foreign intelligence that will prevent a terrorist attack, for example,” the policy reads.
The ASD also considers whether retaining the vulnerability runs the risk of a malicious actor taking advantage of the weakness, as well as what preventative measures might be needed to protect Australian interests.
Newly-discovered vulnerabilities are first assessed by the Equity Steering Group consisting of working-level technical experts. ZDNet understands that both the cybersecurity and offensive cyber operations sides of the ASD are represented, and that the discussions can be robust.
If that group recommends a vulnerability should be retained, it is then considered by the Equity Board made up of officers at the Senior Executive Service pay grades.
See: ACSC tightens access controls for Australian government systems
Decisions to retain vulnerabilities are reviewed quarterly by the director-general, and annually by the independent Inspector General of Intelligence and Security (IGIS). Briefing IGIS to her satisfaction is understood to be a daunting experience.
The retention of each individual vulnerability is also reviewed after 12 months.
ZDNet understands that at the end of this assessment and review process, the number of vulnerabilities retained for ASD use is very small, an amount that would not be characterised as “warehousing”.
Australia’s Huawei ban a ‘resolved’ question: Payne
Australia has made its sovereign decision, says Marise Payne. Other nations will make their own.
Australia should name parliament cyber attackers
In the case of such a blatant attack on Australia’s institutions of government, we should stand ready to point the finger and impose some real costs on the adversary.
Australian web hosts hit with a Manic Menagerie of malware
Criminals used compromised web hosting servers to mine cryptocurrency, and insert advertising and SEO tools into customer websites.
ACSC dumps annual conference, partners with AISA for cyber events
Australia’s cybersecurity agency joins the nation’s peak body for cyber professionals to deliver development programs through the government’s Joint Cyber Security Centres.
Australian government lags UK in deploying DMARC email spoofing prevention
DMARC email authentication can significantly reduce the risk of phishing attacks, but only 5.5 percent of Australia’s main government domains have deployed it. That’s set to change.
Australia’s encryption laws are ‘highly unlikely’ to dragoon employees in secret
Relax, developers, the Assistance and Access Act is ‘highly unlikely’ to force employees to deceive their bosses by creating secret backdoors. Nor does it breach Europe’s GDPR digital privacy laws.
CISO Podcast: Talking Anti-Phishing Solutions
Simon Gibson earlier this year published the report, “GigaOm Radar for Phishing Prevention and Detection,” which assessed more than a dozen security solutions focused on detecting and mitigating email-borne threats and vulnerabilities. As Gibson noted in his report, email remains a prime vector for attack, reflecting the strategic role it plays in corporate communications.
Earlier this week, Gibson’s report was a featured topic of discussions on David Spark’s popular CISO Security Vendor Relationship Podcast. In it, Spark interviewed a pair of chief information security officers—Mike Johnson, CISO for SalesForce, and James Dolph, CISO for Guidewire Software—to get their take on the role of anti-phishing solutions.
“I want to first give GigaOm some credit here for really pointing out the need to decide what to do with detections,” Johnson said when asked for his thoughts about selecting an anti-phishing tool. “I think a lot of companies charge into a solution for anti-phishing without thinking about what they are going to do when the thing triggers.”
As Johnson noted, the needs and vulnerabilities of a large organization aligned on Microsoft 365 are very different from those of a smaller outfit working with GSuite. A malicious Excel macro-laden file, for example, poses a credible threat to a Microsoft shop and therefore argues for a detonation solution to detect and neutralize malicious payloads before they can spread and morph. On the other hand, a smaller company is more exposed to business email compromise (BEC) attacks, since spending authority is often spread among many employees in these businesses.
Gibson’s radar report describes both in-line and out-of-band solutions, but Johnson said cloud-aligned infrastructures argue against traditional in-line schemes.
“If you put an in-line solution in front of [Microsoft] 365 or in front of GSuite, you are likely decreasing your reliability, because you’ve now introduced this single point of failure. Google and Microsoft have this massive amount of reliability that is built in,” Johnson said.
So how should IT decision makers go about selecting an anti-phishing solution? Dolph answered that question with a series of questions of his own:
“Does it nail the basics? Does it fit with the technologies we have in place? And then secondarily, is it reliable, is it tunable, is it manageable?” he asked. “Because it can add a lot overhead, especially if you have a small team if these tools are really disruptive to the email flow.”
Dolph concluded by noting that it’s important for solutions to provide insight that can help organizations target their protections, as well as support both training and awareness around threats. Finally, he urged organizations to consider how they can measure the effectiveness of solutions.
“I may look at other solutions in the future and how do I compare those solutions to the benchmark of what we have in place?”
Listen to the Podcast: CISO Podcast
Phish Fight: Securing Enterprise Communications
Yes, much of the world may have moved on from email to social media and culturally dubious TikTok dances, yet traditional electronic mail remains a foundation of business communication. And sadly, it remains a prime vector for malware, data leakage, and phishing attacks that can undermine enterprise protections. It doesn’t have to be that way.
In a just released report titled “GigaOm Radar for Phishing Prevention and Detection,” GigaOm Analyst Simon Gibson surveyed more than a dozen enterprise-focused email security solutions. He found a range of approaches to securing communications that often can be fitted together to provide critical, defense-in-depth protection against even determined attackers.
Figure 1. GigaOm Radar for Email Phishing Prevention and Detection
“When evaluating these vendors and their solutions, it is important to consider your own business and workflow,” Gibson writes in the report, stressing the need to deploy solutions that best address your organization’s business workflow and email traffic. “For some it may be preferable to settle on one comprehensive solution, while for others building a best-of-breed architecture from multiple vendors may be preferable.”
In a field of competent solutions, Gibson found that Forcepoint, purchased recently by Raytheon, stood apart thanks to the layered protections provided by its Advanced Classification Engine. Area 1 and Zimperium, meanwhile, are both leaders that exhibit significant momentum, with Area 1 boosted by its recent solution partnership with Virtru, and Zimperium excelling in its deep commitment to mobile message security.
A mobile focus is timely, Gibson says in a video interview for GigaOm. He says companies are “tuning the spigot on” and enabling unprecedented access and reliance on mobile devices, which is creating an urgent need to get ahead of threats.
Gibson’s conclusion in the report? He singles out three things: Defense in depth, awareness of existing patterns and infrastructure, and a healthy respect for the “human factor” that can make security so hard to lock down.
When Is a DevSecOps Vendor Not a DevSecOps Vendor?
DevOps’ general aim is to enable a more efficient process for producing software and technology solutions and bringing stakeholders together to speed up delivery. But we know from experience that this inherently creative, outcome-driven approach often forgets about one thing until too late in the process—security. Too often, security is brought into the timeline just before deployment, risking last minute headaches and major delays. The security team is pushed into being the Greek chorus of the process, “ruining everyone’s fun” by demanding changes and slowing things down.
But as we know, in the complex, multi-cloud and containerized environment we find ourselves in, security is becoming more important and challenging than ever. And the costs of security failure are not only measured in slower deployment, but in compliance breaches and reputational damage.
The term “DevSecOps” has been coined to characterize how security needs to be at the heart of the DevOps process. This is in part principle and part tools. As a principle, DevSecOps fits with the concept of “shifting left,” that is, ensuring that security is treated as early as possible in the development process. So far, so simple.
From a tooling perspective, however, things get more complicated, not least because the market has seen a number of platforms marketing themselves as DevSecOps. As we have been writing our Key Criteria report on the subject, we have learned that not all DevSecOps vendors are necessarily DevSecOps vendors. Specifically, we have learned to distinguish capabilities that directly enable the goals of DevSecOps from a process perspective, from those designed to support DevSecOps practices. We could define them as: “Those that do, and those that help.”
This is how to tell the two types of vendor apart and how to use them.
Vendors Enabling DevSecOps: “Tools That Do”
A number of tools work to facilitate the DevSecOps process -– let’s bite the bullet and call them DevSecOps tools. They help teams set out each stage of software development, bringing siloed teams together behind a unified vision that allows fast, high-quality development, with security considerations at its core. DevSecOps tools work across the development process, for example:
- Create: Help to set and implement policy
- Develop: Apply guidance to the process and aid its implementation
- Test: Facilitate and guide security testing procedures
- Deploy: Provide reports to assure confidence to deploy the application
The key element that sets these tool sets apart is the ability to automate and reduce friction within the development process. They will prompt action, stop a team from moving from one stage to another if the process has not adequately addressed security concerns, and guide the roadmap for the development from start to finish.
Supporting DevSecOps: “Tools That Help”
In this category we place those tools which aid the execution, and monitoring, of good DevSecOps principles. Security scanning and application/infrastructure hardening tools are a key element of these processes: Software composition analysis (SCA) forms a part of the development stage, static/dynamic application security testing (SAST/DAST) is integral to the test stage and runtime app protection (RASP) is a key to the Deploy stage.
Tools like this are a vital part of the security layer of security tooling, especially just before deployment – and they often come with APIs so they can be plugged into the CI/CD process. However, while these capabilities are very important to DevSecOps, they can be seen in more of a supporting role, rather than being DevSecOps tools per se.
DevSecOps-washing is not a good idea for the enterprise
While one might argue that security should never have been shifted right, DevSecOps exists to ensure that security best practices take place across the development lifecycle. A corollary exists to the idea of “tools that help,” namely that organizations implementing these tools are not “doing DevSecOps,” any more than vendors providing these tools are DevSecOps vendors.
The only way to “do” DevSecOps is to fully embrace security at a process management and governance level: This means assessing risk, defining policy, setting review gates, and disallowing progress for insecure deliverables. Organizations that embrace DevSecOps can get help from what we are calling DevSecOps tools, as well as from scanning and hardening tools that help support its goals.
At the end of the day, all security and governance boils down to risk: If you buy a scanning tool so you can check a box that says “DevSecOps,” you are potentially adding to your risk posture, rather than mitigating it. So, get your DevSecOps strategy fixed first, then consider how you can add automation, visibility, and control using “tools that do,” as well as benefit from “tools that help.”
Tencent-backed Hike, once India’s answer to WhatsApp, has given up on messaging – TechCrunch
India’s answer to WhatsApp has completely moved on from messaging. Hike Messenger, backed by Tencent, Tiger Global and SoftBank and...
Google Maps adds new details in four major cities
Google Maps is adding some new details in four major cities scattered around the world that will make it easier...
Hyperion XP-1 hydrogen supercar has landed in Las Vegas
The Hyperion XP-1, touted as the world’s first hydrogen fuel cell supercar, has recently landed in Las Vegas to the...
Twitter is bringing Moments to Indian social app Dailyhunt – TechCrunch
Five years after its launch, Twitter Moments is growing beyond the American social networking platform. On Monday, Twitter said it...
Bluetti AC200P Power Station Review
When it comes to batteries, you almost always have to make a compromise between power and size. That’s more true...
Social12 months ago
CrashPlan for Small Business Review
Gadgets2 years ago
A fictional Facebook Portal videochat with Mark Zuckerberg – TechCrunch
Mobile2 years ago
Memory raises $5M to bring AI to time tracking – TechCrunch
Social2 years ago
iPhone XS priciest yet in South Korea
Cars2 years ago
What’s the best cloud storage for you?
Security2 years ago
Google latest cloud to be Australian government certified
Social2 years ago
Apple’s new iPad Pro aims to keep enterprise momentum
Cars2 years ago
Some internet outages predicted for the coming month as ‘768k Day’ approaches