Black Friday Our software, PenTest Project: Slate Enterprise at €53 instead of €173 per user a month, and Flint free for 12 months. Until 30 November. See the offer →
PenTest Hub logo

Libraries · SDKs · Plug-ins · Integrations

Third-Party Integration Security Testing

Every library, SDK, plug-in and connected service extends your attack surface. We test the risks they bring into your applications: supply chain weaknesses, broken trust boundaries and poor API hygiene.

  • Libraries, SDKs and plug-ins
  • Trust boundaries
  • Supply chain risk
Sample findings · Integration reviewSample
CRITICALOutdated plug-in with a public remote code exploitInstalled on the customer portal
HIGHWebhook accepts requests without a signatureAnyone can trigger order updates
HIGHIntegration token has full account accessOnly read access to two objects was needed
MEDIUMAnalytics SDK sends personal data to a third partyNot listed in the privacy notice
Each finding with evidence, a risk rating and a fixSample findings

In one sentence

What is third-party integration testing?

Third-party integration testing assesses the risks introduced into your applications by external modules, libraries, SDKs, plug-ins and connected services, including supply chain issues, trust boundaries and the way you exchange data with them.

You inherit the weaknesses of every component you use and every service you trust. We look at what each integration can do, what it can reach, and what happens if it is compromised.

Typical integrations

  • Open-source libraries and frameworks
  • Mobile and web SDKs (analytics, payments, chat)
  • CMS and e-commerce plug-ins
  • Webhooks, OAuth apps and API connections to SaaS services

Scope

What we test

Each component you depend on and each service you connect to.

Libraries and dependencies

Known vulnerabilities, outdated versions and risky dependencies in the components your applications use.

  • Dependencies
  • Known vulnerabilities
  • Versions

SDKs

What embedded SDKs collect, where they send it and what permissions they need.

  • Data flows
  • Permissions
  • Privacy

Plug-ins and extensions

Plug-ins for your CMS, e-commerce platform or tools, and what they expose.

  • CMS
  • E-commerce
  • Extensions

Webhooks and API connections

Authentication, signatures and input handling on the connections between your systems and others.

  • Webhooks
  • OAuth
  • API keys

Trust boundaries

What a connected service is allowed to do, and whether it has more access than it needs.

  • Least privilege
  • Scopes
  • Tokens

Supply chain scenarios

What an attacker could do if a supplier or component were compromised.

  • Compromise
  • Impact
  • Containment

Approach

Testing approaches based on access

Choose how much you share with us. More context means deeper coverage in the same time.

No prior knowledge

Black box

We test the integrations exposed to the internet as an outside attacker would.

Accounts and some context

Grey box

With accounts and an overview of your integrations, we test trust boundaries and data flows.

Full access

White box

With access to configurations, dependency lists and code, we review each integration in depth.

Engagement

How we work with you

  1. Scope online

    Describe what you need in Flint, our scoping platform. Answer only the questions that apply.

  2. Proposal, signed online

    Effort, price and the statement of work are built from your answers.

  3. Ready for day one

    Authorisation, test accounts and rules of engagement are agreed before testing starts.

  4. Senior-led testing

    Certified consultants lead the test. Our own AI framework, Striker AI, takes on the repetitive work.

  5. Report and retest

    Your report is ready in Slate, our client portal, within 48 hours of testing ending.

What you receive

Everything stays in one place, in your own client portal.

  • A report in Slate within 48 hours of testing ending
  • Every finding with evidence, a risk rating and a fix
  • An executive summary for leadership
  • Retests you can request finding by finding
  • Downloads as PDF or Excel
  • Evidence you can hand to your auditors

Standards

Standards we test against

Aligned with the frameworks your developers and auditors use.

  • OWASP Top 10
  • OWASP API Security Top 10
  • CREST guidance
  • NIST SP 800-53
  • ISO/IEC 27001

FAQ

Frequently asked questions

Can't find yours? Ask a senior tester and we'll reply directly.

What counts as a third-party integration?
Any component or service you did not build but rely on: libraries, SDKs, plug-ins, and connections to SaaS platforms through APIs, OAuth or webhooks.
Do you test the third party itself?
No. We test how the integration behaves in your environment and what it can reach. Testing a supplier's own systems needs their permission.
Can this be part of an application test?
Yes. It is often added to a web or mobile application test, or run on its own for platforms with many integrations.
What do you need from us?
A list of the integrations in scope, test accounts and, for deeper review, dependency lists or configuration access.
When will we receive the report?
Within 48 hours of testing ending, in Slate, our client portal.

Contact

Tell us what you need to test

A senior tester reads every message and replies directly.