Skip to main content
    Legacy Vendor Exposure

    FedEx Bongo International Legacy Vendor Exposure (2018)

    Breach Year

    2018

    Breach Type

    Legacy Vendor Exposure

    TPRM Lesson

    Acquired vendors bring acquired exposure.

    What was the FedEx Bongo International Legacy Vendor Exposure breach?

    The FedEx Bongo International exposure was a 2018 incident in which 119,000+ scanned identity documents from customers of Bongo International, a company FedEx acquired in 2014 and later rebranded, were found publicly accessible in an unsecured Amazon S3 bucket.

    FedEx Bongo is the case that showed acquired vendors bring acquired exposure.

    Bongo International was a package forwarding service that scanned customer passports, driving licences and other identity documents to comply with export rules.

    FedEx acquired Bongo in 2014 and later folded it into FedEx Cross-Border, which was shut down in 2017. The scanned documents remained in an unsecured S3 bucket until researchers found them in early 2018.

    What Was It?

    A legacy storage bucket from an acquired subsidiary that outlived the business it served.

    What Happened?

    2009 to 2014. Bongo International collected scanned ID documents for compliance.

    2014. FedEx acquired Bongo.

    2017. The rebranded FedEx Cross-Border service was closed.

    Feb 2018. Researchers at Kromtech Security found the open S3 bucket with 119,000+ scanned documents.

    How Did It Happen Technically?

    • An S3 bucket used by Bongo was left with public ACLs after the business shut down.
    • Post-acquisition data inventory did not capture the bucket.
    • No lifecycle policy deleted the documents.
    • No monitoring flagged the public access configuration.

    Why This Was a TPRM Failure

    • Acquisition due diligence missed the data store. The bucket was never inventoried.
    • No retention or deletion policy. Compliance scans lived on for years after the business closed.
    • No configuration monitoring. Public S3 access went undetected.
    • Sub-vendor tooling ignored. Bongo's cloud footprint was inherited without a security review.

    Business Impact

    • 119,000+ scanned identity documents exposed.
    • Reputational damage to FedEx despite no active service being affected.
    • Industry attention on post-acquisition data hygiene.

    Consequences

    The case accelerated adoption of acquisition-triggered cloud inventory and mandatory deletion of collected identity documents once the business purpose ends.

    What Most People Miss About This Breach

    No attack occurred. The vendor was simply forgotten. Legacy exposure is a TPRM problem even when nobody breaches anything.

    Practical TPRM Lessons

    1. Run cloud-account inventory as a mandatory M&A step.
    2. Apply retention and deletion policies to identity documents at collection time.
    3. Monitor S3 and equivalent buckets for public access.
    4. Sunset acquired brands with a documented data-destruction plan.
    5. Include acquired vendors in vendor register from day one.
    6. Contractually require deletion evidence when a subsidiary closes.
    7. Automate policy enforcement across cloud accounts.
    8. Report legacy-vendor exposure to the board.

    Technical Protection Checklist

    A. Identity and Access. MFA and least privilege on all inherited cloud accounts.

    B. SaaS and API Integrations. Inventory every cloud service from an acquired entity.

    C. Software Supply Chain. Deprecate inherited tools with a plan, not by neglect.

    D. File Transfer and Data Exchange. Enforce bucket-level public-access blocks by policy.

    E. Data Protection. Encrypt at rest and enforce retention deletion.

    F. Vendor Incident Response. Include acquired brands in IR runbooks.

    G. Fourth-Party Risk. Discover cloud sub-vendors during due diligence.

    H. Board and Executive Reporting. Report acquired-brand data footprint quarterly.

    Final TPRM Takeaway

    "When you buy a business you inherit its buckets. Inventory them or own them anyway."

    Frequently Asked Questions

    What was the FedEx Bongo exposure?

    A 2018 discovery of 119,000+ scanned ID documents in an open S3 bucket from a FedEx-acquired subsidiary.

    Why is it considered a third-party breach?

    The exposure stemmed from a subsidiary's inherited cloud footprint that FedEx did not inventory.

    How did it happen?

    The S3 bucket was left publicly accessible after the acquired business was closed.

    What was exposed?

    Passports, driving licences and other identity documents.

    What was the impact?

    Reputational damage and industry rethink of post-acquisition data hygiene.

    What controls could have reduced the risk?

    M&A cloud inventory, retention deletion and continuous public-access monitoring.

    What should TPRM teams learn?

    Acquired vendors bring inherited exposure that must be governed from day one.

    What is the biggest lesson?

    Forgotten vendors are still your vendors.

    TPRM Blog

    Related TPRM analysis from the blog

    Continue learning with the latest breach alerts, regulatory updates, and analyst playbooks from blog.learntprm.com.

    Visit blog.learntprm.com
    Safe Security - founding sponsor of LearnTPRM.comFounding Sponsor
    For CISOs, TPRM leads and vendor risk program owners

    Autonomous TPRM. 90% less manual effort.

    Almost every case here was findable before it happened

    Read enough third-party breaches and the pattern is brutal: an undisclosed fourth party, an expired certification, an exposure that sat on the internet for weeks. Nobody was lazy - the signals simply arrive faster than a human review cycle. The SAFE TPRM AI Co-Worker watches for them continuously.

    This is for you if you own a third-party risk program - roughly 100+ vendors, quarterly reassessments, DORA / NIS2 / OCC pressure and no new headcount coming. The link opens Safe Security's platform page, not a gated form.

    Five correlated data dimensions per vendor, refreshed continuously across the whole portfolio.

    Zero-touch due diligenceContinuous monitoring across 5 dimensionsAI-powered risk scoring workflows
    • The Fourth-Party Discovery agent finds the undisclosed downstream provider before it becomes your incident.
    • The Outside-In agent detects new vulnerabilities, misconfigurations and breaches as they surface.
    • The Threat Intel agent tracks leaked credentials, filings and legal events per vendor.
    Evaluate SAFE for my organization

    For security and risk leaders assessing a TPRM platform. Opens safe.security in a new tab.

    25+

    AI agents

    90%

    Less manual effort

    None

    Additional headcount

    200+

    Organizations globally

    End to end

    Intake to offboarding

    Ready to Prove You're a TPRM Warrior?

    Most people talk about risk management. Few can prove their expertise under pressure.

    Start Your Free Certification