Incident sheet · /security

Filed
Read
3 min · 592 words
Severity
Routine

Infoblox confirms breach through compromised migration vendor

Infoblox confirms unauthorized access through a compromised SharePoint migration vendor. One source says sensitive customer data was taken, but the number of affected customers remains undisclosed.

Cyber giant Infoblox confirms security incident after hackers access ‘company information’
FeedCyber giant Infoblox confirms security incident after hackers access ‘company information’ — Albert Stoynov / unsplash

Event log

  1. The disclosed entry route was a compromised third-party data migration vendor.
  2. An Infoblox notification and two knowledgeable sources identified an unnamed vendor that provides SharePoint data migration services.
  3. One knowledgeable source said sensitive customer data was taken; Infoblox has not disclosed the customer count.
  4. Infoblox hosts much of its files, emails and infrastructure with Microsoft, including a SharePoint server accessible through its single sign-on provider.
  5. Infoblox reports no indication that its products, cloud services, software updates or build-and-release processes were involved.

By Amara Osei

Infoblox confirmed a cybersecurity incident in which hackers accessed certain company information through a compromised third-party data migration vendor, making a compromised supplier the disclosed route rather than a confirmed flaw in its own platform.

What does Infoblox know about the incident?

An Infoblox spokesperson told TechCrunch that the company was investigating unauthorized access to certain company information through a compromised third-party data migration vendor.

The spokesperson added: “We immediately activated our incident response procedures, took steps to contain the incident and are working with leading outside cybersecurity experts to investigate the facts, understand the scope and address any confirmed risks.”

Infoblox is a privately held cybersecurity and automation company that provides domain name resolution, identity and user access management, and other networking services. That makes the distinction between compromise of a supplier and compromise of Infoblox's own systems central to enterprise risk assessment.

Takeaway: The company has identified a third-party route and started containment, but it has not quantified the exposure.

How did the vendor enter the breach?

TechCrunch learned that the vendor provides SharePoint data migration services, based on an Infoblox notification about the breach. Two people with knowledge of the incident also told TechCrunch about the vendor. The supplier therefore handled data transfer for Infoblox, creating the disclosed route into company information.

Infoblox has not named the vendor. One person with knowledge said Infoblox had terminated its work with the supplier; the spokesperson did not comment on that account. One person with knowledge also said sensitive customer data was taken. Infoblox has not identified the data categories or the number of affected customers.

Takeaway: The migration vendor is the disclosed route, and the report that customer data was taken still rests on one source.

Where did Infoblox hold the information?

Public internet records seen by TechCrunch show that Infoblox hosts much of its files, emails and infrastructure with Microsoft, including a SharePoint server. TechCrunch confirmed that the server was accessible through Infoblox's single sign-on provider.

SharePoint is web-based software that companies use to share and host internal files and documents. These records map the environment that the migration work touched, but they do not show that attackers compromised SharePoint, Microsoft or the single sign-on provider.

Takeaway: The records identify where data sat; the vendor remains the only disclosed access route.

What has Infoblox said was uninvolved?

The spokesperson said there was “no indication that any Infoblox products, cloud services, software updates or build-and-release processes were involved” in the breach.

That wording defines four areas not implicated by current evidence:

  • Infoblox products.
  • Cloud services.
  • Software updates.
  • Build-and-release processes.

“No indication” is not the same as a final forensic clearance, and it does not answer how many customer records left Infoblox's control.

Takeaway: Infoblox has separated the incident from its core product and release processes, without yet closing the customer-impact assessment.

What remains unresolved?

Infoblox would not say how many customers the incident affected or clarify whether it knew of affected customers at that time. It also did not say whether hackers had contacted the company or made demands.

The open questions are therefore specific: the size of the customer population, the nature and volume of information taken, the vendor's access during migration, and any attacker demands. Outside cybersecurity experts are working with Infoblox to establish those facts and address confirmed risks.

Until the investigation produces a final scope, executives cannot use the absence of product involvement to assume customer exposure was limited.

via techcrunch.com (Source)

Filed under

  • infoblox
  • data-breach
  • third-party-risk
  • supply-chain-security
  • incident-response
Share this article:

More from Amara Osei

Amara Osei

Show full bio

Correspondent covering regulation, policy and their impact on enterprise information technology and the leaders who run at CIO Monitor.

188 articles

The newsroom digest

One email a day with the stories that matter. No noise.

By subscribing you agree to the privacy policy.

Cross-references

‹ Previous articleNext article ›