Connect with us

Security

Australia’s cybersecurity chief Alastair MacGibbon resigns

Published

on

Alastair MacGibbon, the head of the Australian Cyber Security Centre (ACSC), has tendered his resignation and will return to the private sector.

MacGibbon led the ACSC since January 2018, when it first became part of the Australian Signals Directorate (ASD).

He also held the title of National Cyber Security Adviser at the Department of Home Affairs (DHA), where he was charged with the implementation of government’s Cyber Security Strategy.

ASD director-general Mike Burgess said in a statement on Saturday that he regretted the announcement of MacGibbon’s resignation, saying that MacGibbon “leaves a considerable legacy”.

“Alastair has been a fierce advocate for the importance of cyber security for the community, businesses and governments. He is indeed the face of cyber security in Australia and, through his leadership, helped raise the nation’s cyber security standards,” Burgess said.

During his time at the ACSC, MacGibbon oversaw the transition of other parts of government into the newly-independent ASD as it became a statutory authority.

He also oversaw the completion of the network of Joint Cyber Security Centres (JCSC) for coordination with the private sector, a reshaping of the government’s Information Security Manual (ISM), and a tightening of access controls for government systems as part of a new Essential Eight Maturity Model.

Prior to his ACSC role, MacGibbon was then-Prime Minister Malcolm Turnbull’s Special Adviser on Cyber Security, during which he led an investigation into the debacle that was the the 2016 Census.

And prior to that, from April 2015, MacGibbon was Australia’s first eSafety Commission. In that role, his office achieved a remarkable amount of work in its first 12 months.

The perfect time to leave

“Alastair believes the end of the electoral cycle is an appropriate time for renewal,” Burgess said of MacGibbon’s departure from the ACSC.

The timing makes sense, and not just because MacGibbon’s work at the agency had reached a natural inflection point.

It’s also just days until Australia’s federal election on May 18, an election that the Labor opposition is widely expected to win. At least at this stage.

For at least a year now, the consensus of the Canberra rumour mill has been that a Labor government would dismantle DHA. Word is that some public servants who were transferred into the new mega-department hadn’t bothered printing new business cards because they expected their previous places in the bureaucracy would soon return.

The expectation is not unreasonable. The creation of DHA was as much a political act as it was organisational development.

It was driven in part by power struggles within the Coalition government — particularly the need for then-Prime Minister Turnbull to slap down Australia’s then-favourite attorney-general, Senator George Brandis QC, in order to placate then-Immigration and Border Protection Minister Peter Dutton.

Your writer also understands that DHA isn’t a happy ship at the moment.

There’s dissatisfaction with the apparent lack of efficiency in certain areas, including the cybers. MacGibbon’s twin hat roles, reporting to both DHA for policy matters and ASD for operational concerns, could not have been easy.

MacGibbon has spent the past 17 months getting that curious structure to work. I can’t imagine he would have been thrilled about the prospect of having to take it apart again.

He was also a Coalition choice, having originally been chosen for the special adviser role personally by Turnbull. That presumably put some noses out of joint at the Department of Prime Minister and Cabinet (PM&C), where some senior staff might have been eyeing the job for themselves.

The partisan politicisation of the public service is a disappointing reality. Axing the department or axing the person might well appeal to a new government wanting to make its mark.

Should the Coalition manage to win the election and remain in power, however, it’s likely there would be a new minister for Home Affairs. Peter Dutton holds his seat by a narrow margin, and is likely to exit Parliament even if his side wins.

Ministerial attention to cybersecurity has already gone missing under Prime Minister Scott Morrison. What would the future hold?

All this is speculation, however.

MacGibbon’s final day with ASD will be May 28. Until the role is permanently filled, the ACSC will be led by Lieutenant General John Frewen, the ASD’s Principal Deputy Director-General.

Alastair MacGibbon has been contacted for comment.

Related Coverage

Morrison pledges AU$156m to build cyber workforce and fight cybercrime if re-elected

The multi-million dollar investment will be used to thwart ‘organised cybercrime gangs’, build a cyber workforce, and help small businesses stay protected.

ASIO eyes Microsoft Azure for phase one of tech transformation

Six packages are up for grabs under the spy agency’s systems integration tender, with protected, secret, and top secret information to be hosted solely on Azure.

Australian Budget 2019: Census 2021 gets AU$38m to ‘address issues from 2016’

Almost AU$40 million in additional funding will be provided to the ABS that aims to prevent incidents like the 2016 Census debacle from reoccurring in 2021, while the government will continue to digitise its services.

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.

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.

Source link

Continue Reading
Click to comment

Leave a Reply

Your email address will not be published. Required fields are marked *

Security

CISO Podcast: Talking Anti-Phishing Solutions

Published

on

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

Continue Reading

Security

Phish Fight: Securing Enterprise Communications

Published

on

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.

Continue Reading

Security

When Is a DevSecOps Vendor Not a DevSecOps Vendor?

Published

on

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.”

Continue Reading

Trending