<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>ProcureCortex blog</title>
    <link>https://procurecortex.com/blog</link>
    <atom:link href="https://procurecortex.com/blog/rss.xml" rel="self" type="application/rss+xml"/>
    <description>Guides, checklists and worked examples on vendor risk assessment, SOC 2 reports, DPAs, DORA and NIS2, written for practitioners.</description>
    <language>en-gb</language>
    <lastBuildDate>Fri, 30 Oct 2026 09:00:00 GMT</lastBuildDate>
    <image><url>https://procurecortex.com/apple-touch-icon.png</url><title>ProcureCortex blog</title><link>https://procurecortex.com/blog</link></image>
    <item>
      <title>AI agents are your newest third parties: MCP servers, plugins and skills as vendor risk</title>
      <link>https://procurecortex.com/blog/ai-agents-third-party-risk-mcp</link>
      <guid isPermaLink="true">https://procurecortex.com/blog/ai-agents-third-party-risk-mcp</guid>
      <pubDate>Fri, 30 Oct 2026 09:00:00 GMT</pubDate>
      <category>Third-Party Risk</category>
      <description>AI agents load tools, connectors and skills at runtime. Each one is a dependency with access to your data. What to add to vendor intake before the next one is installed.</description>
      <enclosure url="https://procurecortex.com/covers/ai-agents-third-party-risk-mcp.jpg" type="image/jpeg" length="74801"/>
    </item>
    <item>
      <title>Your vendor's product is being actively exploited: a 72-hour third-party incident playbook</title>
      <link>https://procurecortex.com/blog/vendor-actively-exploited-vulnerability-playbook</link>
      <guid isPermaLink="true">https://procurecortex.com/blog/vendor-actively-exploited-vulnerability-playbook</guid>
      <pubDate>Wed, 28 Oct 2026 09:00:00 GMT</pubDate>
      <category>Compliance</category>
      <description>A supplier's product you run has an actively exploited flaw. What to do in the first 4, 24 and 72 hours, and how the vendor's CRA clock lines up with your DORA, NIS2 and GDPR clocks.</description>
      <enclosure url="https://procurecortex.com/covers/vendor-actively-exploited-vulnerability-playbook.jpg" type="image/jpeg" length="118293"/>
    </item>
    <item>
      <title>The Cyber Resilience Act is live: what it means for the software vendors you buy from</title>
      <link>https://procurecortex.com/blog/cyber-resilience-act-software-vendors</link>
      <guid isPermaLink="true">https://procurecortex.com/blog/cyber-resilience-act-software-vendors</guid>
      <pubDate>Mon, 26 Oct 2026 09:00:00 GMT</pubDate>
      <category>Compliance</category>
      <description>Since 11 September 2026, software makers must report actively exploited vulnerabilities within 24 hours. What that changes for the vendors you buy from, and what to ask them now.</description>
      <enclosure url="https://procurecortex.com/covers/cyber-resilience-act-software-vendors.jpg" type="image/jpeg" length="124199"/>
    </item>
    <item>
      <title>One SOC 2 report, two workflows: manual review vs ProcureCortex</title>
      <link>https://procurecortex.com/blog/one-soc-2-report-two-workflows</link>
      <guid isPermaLink="true">https://procurecortex.com/blog/one-soc-2-report-two-workflows</guid>
      <pubDate>Fri, 23 Oct 2026 09:00:00 GMT</pubDate>
      <category>Vendor Risk</category>
      <description>The same SOC 2 report, reviewed twice: once by hand with a spreadsheet, once with findings linked to the page they came from and a recorded decision. Step by step.</description>
      <enclosure url="https://procurecortex.com/covers/one-soc-2-report-two-workflows.jpg" type="image/jpeg" length="108975"/>
    </item>
    <item>
      <title>The AI Act delay explained: what changed for AI vendor due diligence, and what didn't</title>
      <link>https://procurecortex.com/blog/eu-ai-act-delay-ai-vendor-due-diligence</link>
      <guid isPermaLink="true">https://procurecortex.com/blog/eu-ai-act-delay-ai-vendor-due-diligence</guid>
      <pubDate>Wed, 21 Oct 2026 09:00:00 GMT</pubDate>
      <category>Compliance</category>
      <description>The high-risk AI rules now start in December 2027 and August 2028. Transparency, AI literacy and your GDPR duties did not move. What to keep asking AI vendors.</description>
      <enclosure url="https://procurecortex.com/covers/eu-ai-act-delay-ai-vendor-due-diligence.jpg" type="image/jpeg" length="176226"/>
    </item>
    <item>
      <title>Fourth-party risk when everyone runs on the same 19 providers</title>
      <link>https://procurecortex.com/blog/fourth-party-risk-concentration-ctpp</link>
      <guid isPermaLink="true">https://procurecortex.com/blog/fourth-party-risk-concentration-ctpp</guid>
      <pubDate>Mon, 19 Oct 2026 09:00:00 GMT</pubDate>
      <category>Vendor Risk</category>
      <description>Your vendors run on the same few cloud and ICT providers. What DORA, NIS2 and GDPR expect you to know about who sits behind them.</description>
      <enclosure url="https://procurecortex.com/covers/fourth-party-risk-concentration-ctpp.jpg" type="image/jpeg" length="93301"/>
    </item>
    <item>
      <title>AI vendor assessment: from the DPA to a defensible finding</title>
      <link>https://procurecortex.com/blog/ai-vendor-assessment-dpa-to-finding</link>
      <guid isPermaLink="true">https://procurecortex.com/blog/ai-vendor-assessment-dpa-to-finding</guid>
      <pubDate>Wed, 14 Oct 2026 09:00:00 GMT</pubDate>
      <category>Vendor Risk</category>
      <description>To assess an AI vendor from its DPA, check whether the agreement still describes what the product does today. In this illustrative example, a 2024 DPA did not cover a 2026 feature that sent customer documents to a model provider. Checked against GDPR Article 28(2), the sub-processor clause produced a high-severity finding that cited clause, page and rule.</description>
      <enclosure url="https://procurecortex.com/covers/ai-vendor-assessment-dpa-to-finding.jpg" type="image/jpeg" length="113425"/>
    </item>
    <item>
      <title>NIS2 supply chain security: what Article 21 means for suppliers</title>
      <link>https://procurecortex.com/blog/nis2-supply-chain-security-suppliers</link>
      <guid isPermaLink="true">https://procurecortex.com/blog/nis2-supply-chain-security-suppliers</guid>
      <pubDate>Mon, 12 Oct 2026 09:00:00 GMT</pubDate>
      <category>Security</category>
      <description>NIS2 Article 21(2)(d) requires essential and important entities to manage supply chain security, including the security of their relationships with direct suppliers and service providers. Suppliers outside NIS2's scope still feel it through contracts, questionnaires and evidence requests. Expect to show secure development, vulnerability handling, incident notification and access control with documents, not assurances.</description>
      <enclosure url="https://procurecortex.com/covers/nis2-supply-chain-security-suppliers.jpg" type="image/jpeg" length="151738"/>
    </item>
    <item>
      <title>DORA vendor evidence in practice: mapping a SOC 2, DPA and continuity plan in one review</title>
      <link>https://procurecortex.com/blog/dora-vendor-evidence-soc-2-dpa-bcp</link>
      <guid isPermaLink="true">https://procurecortex.com/blog/dora-vendor-evidence-soc-2-dpa-bcp</guid>
      <pubDate>Thu, 08 Oct 2026 09:00:00 GMT</pubDate>
      <category>Compliance</category>
      <description>Map all three documents to one DORA requirement set instead of reviewing each in isolation. The SOC 2 report shows which controls operated over a period, the DPA shows what the vendor has committed to do with data, and the continuity plan shows how service recovers. Gaps appear where no document covers a requirement or where documents disagree.</description>
      <enclosure url="https://procurecortex.com/covers/dora-vendor-evidence-soc-2-dpa-bcp.jpg" type="image/jpeg" length="109209"/>
    </item>
    <item>
      <title>DORA Article 30 checklist: the mandatory contract clauses and the vendor documents that prove them</title>
      <link>https://procurecortex.com/blog/dora-article-30-contract-checklist</link>
      <guid isPermaLink="true">https://procurecortex.com/blog/dora-article-30-contract-checklist</guid>
      <pubDate>Wed, 07 Oct 2026 09:00:00 GMT</pubDate>
      <category>Compliance</category>
      <description>DORA Article 30 sets the minimum content of every contract between a financial entity and an ICT third-party service provider. Article 30(2) lists nine provisions for all ICT contracts. Article 30(3) adds six more where the service supports a critical or important function. Each clause should be matched to vendor evidence that the control actually operates.</description>
      <enclosure url="https://procurecortex.com/covers/dora-article-30-contract-checklist.jpg" type="image/jpeg" length="103458"/>
    </item>
    <item>
      <title>DORA third-party risk explained: what changes for your ICT vendors</title>
      <link>https://procurecortex.com/blog/dora-third-party-risk-ict-vendors</link>
      <guid isPermaLink="true">https://procurecortex.com/blog/dora-third-party-risk-ict-vendors</guid>
      <pubDate>Mon, 05 Oct 2026 09:00:00 GMT</pubDate>
      <category>Third-Party Risk</category>
      <description>DORA does not regulate most ICT vendors directly. It regulates the financial entities that use them, so its requirements reach vendors through due diligence, contracts and oversight. Since 17 January 2025, entities must keep a register of ICT arrangements, assess providers before signing, include Article 30 clauses and maintain exit plans. Only designated critical providers face direct EU oversight.</description>
      <enclosure url="https://procurecortex.com/covers/dora-third-party-risk-ict-vendors.jpg" type="image/jpeg" length="100697"/>
    </item>
    <item>
      <title>Vendor risk management in 2026: from periodic assessments to continuous intelligence</title>
      <link>https://procurecortex.com/blog/vendor-risk-management-2026-continuous-intelligence</link>
      <guid isPermaLink="true">https://procurecortex.com/blog/vendor-risk-management-2026-continuous-intelligence</guid>
      <pubDate>Fri, 18 Sep 2026 09:00:00 GMT</pubDate>
      <category>Vendor Risk</category>
      <description>Vendor risk management is the work of identifying, assessing and controlling the risks third parties bring, from selection to exit. The annual questionnaire cycle misses most change. In 2026 the stronger model is event-driven: tier vendors at intake, then reassess against fresh evidence whenever a report expires, terms change, a sub-processor is added or an incident is notified.</description>
      <enclosure url="https://procurecortex.com/covers/vendor-risk-management-2026-continuous-intelligence.jpg" type="image/jpeg" length="107186"/>
    </item>
    <item>
      <title>What is AI vendor risk? A guide to evaluating third-party AI providers</title>
      <link>https://procurecortex.com/blog/what-is-ai-vendor-risk</link>
      <guid isPermaLink="true">https://procurecortex.com/blog/what-is-ai-vendor-risk</guid>
      <pubDate>Fri, 04 Sep 2026 09:00:00 GMT</pubDate>
      <category>Vendor Risk</category>
      <description>AI vendor risk is the risk created when a third party's AI system processes your data or shapes your decisions. It covers training on customer data, model providers acting as sub-processors, output reliability, retention of prompts and outputs, and duties under the GDPR and the EU AI Act. Most of it is visible in the vendor's terms, DPA and documentation.</description>
      <enclosure url="https://procurecortex.com/covers/what-is-ai-vendor-risk.jpg" type="image/jpeg" length="73325"/>
    </item>
    <item>
      <title>The vendor risk assessment guide for enterprise teams</title>
      <link>https://procurecortex.com/blog/vendor-risk-assessment-guide</link>
      <guid isPermaLink="true">https://procurecortex.com/blog/vendor-risk-assessment-guide</guid>
      <pubDate>Tue, 14 Jul 2026 09:00:00 GMT</pubDate>
      <category>Vendor Risk</category>
      <description>A vendor risk assessment decides whether a third party's risk is acceptable for the service it will provide. Scope the service, tier the vendor, collect the documents that tier requires, review each against named requirements and record findings with their evidence. Then decide: approve, approve with conditions or decline. Questionnaires fill gaps in the evidence; they do not replace it.</description>
      <enclosure url="https://procurecortex.com/covers/vendor-risk-assessment-guide.jpg" type="image/jpeg" length="161973"/>
    </item>
    <item>
      <title>Vendor risk assessment checklist</title>
      <link>https://procurecortex.com/blog/vendor-risk-assessment-checklist</link>
      <guid isPermaLink="true">https://procurecortex.com/blog/vendor-risk-assessment-checklist</guid>
      <pubDate>Sun, 28 Jun 2026 09:00:00 GMT</pubDate>
      <category>Procurement</category>
      <description>A vendor risk assessment checklist covers five stages: intake (what the vendor will do and touch), tiering (how much scrutiny that deserves), evidence (the documents each tier requires), review (findings against named requirements) and decision (approve, approve with conditions or reject, with the reason recorded). Each stage should leave a record an auditor can follow.</description>
      <enclosure url="https://procurecortex.com/covers/vendor-risk-assessment-checklist.jpg" type="image/jpeg" length="99700"/>
    </item>
    <item>
      <title>How to review vendor SOC 2 reports at scale</title>
      <link>https://procurecortex.com/blog/review-soc-2-reports-at-scale</link>
      <guid isPermaLink="true">https://procurecortex.com/blog/review-soc-2-reports-at-scale</guid>
      <pubDate>Tue, 09 Jun 2026 09:00:00 GMT</pubDate>
      <category>Security</category>
      <description>To review SOC 2 reports at scale, read every report in the same order: the auditor's opinion, the scope and period, the system description and any carve-outs, the exceptions in the testing section, and the complementary user entity controls. Record the same fields each time so reviews compare. A bridge letter is management's statement, not audited evidence.</description>
      <enclosure url="https://procurecortex.com/covers/review-soc-2-reports-at-scale.jpg" type="image/jpeg" length="106477"/>
    </item>
    <item>
      <title>SOC 2 vs ISO 27001 for vendor assessment</title>
      <link>https://procurecortex.com/blog/soc-2-vs-iso-27001-vendor-assessment</link>
      <guid isPermaLink="true">https://procurecortex.com/blog/soc-2-vs-iso-27001-vendor-assessment</guid>
      <pubDate>Thu, 21 May 2026 09:00:00 GMT</pubDate>
      <category>Security</category>
      <description>SOC 2 is an auditor's report on whether a vendor's controls were suitably designed and, in a Type II, operated effectively over a period, with the test results included. ISO/IEC 27001 is a certificate that the vendor's information security management system meets the standard, with a scope but no test results. Neither covers contract or privacy terms.</description>
      <enclosure url="https://procurecortex.com/covers/soc-2-vs-iso-27001-vendor-assessment.jpg" type="image/jpeg" length="98961"/>
    </item>
    <item>
      <title>GDPR vendor due diligence: what to look for in a DPA</title>
      <link>https://procurecortex.com/blog/gdpr-vendor-due-diligence</link>
      <guid isPermaLink="true">https://procurecortex.com/blog/gdpr-vendor-due-diligence</guid>
      <pubDate>Sat, 02 May 2026 09:00:00 GMT</pubDate>
      <category>Compliance</category>
      <description>A data processing agreement must cover everything GDPR Article 28(3) lists: subject matter, duration, nature and purpose, data types, data subjects, documented instructions, confidentiality, security, sub-processors, assistance, deletion or return, and audits. Due diligence means checking each clause is specific, matches the real service, and that sub-processor and transfer terms hold up.</description>
      <enclosure url="https://procurecortex.com/covers/gdpr-vendor-due-diligence.jpg" type="image/jpeg" length="95124"/>
    </item>
    <item>
      <title>Third-party risk vs vendor risk: why the distinction matters</title>
      <link>https://procurecortex.com/blog/third-party-risk-vs-vendor-risk</link>
      <guid isPermaLink="true">https://procurecortex.com/blog/third-party-risk-vs-vendor-risk</guid>
      <pubDate>Thu, 16 Apr 2026 09:00:00 GMT</pubDate>
      <category>Third-Party Risk</category>
      <description>Vendor risk is the risk from suppliers you pay for goods or services. Third-party risk is wider: it also covers distributors, agents, resellers, joint-venture partners and other intermediaries that act with or for you. The distinction matters because triggers, owners, evidence and regulations differ, and a programme built only for vendors misses intermediaries.</description>
      <enclosure url="https://procurecortex.com/covers/third-party-risk-vs-vendor-risk.jpg" type="image/jpeg" length="84566"/>
    </item>
    <item>
      <title>Continuous vendor monitoring without continuous busywork</title>
      <link>https://procurecortex.com/blog/continuous-vendor-monitoring</link>
      <guid isPermaLink="true">https://procurecortex.com/blog/continuous-vendor-monitoring</guid>
      <pubDate>Mon, 30 Mar 2026 09:00:00 GMT</pubDate>
      <category>Third-Party Risk</category>
      <description>Continuous vendor monitoring does not mean reviewing every vendor all the time. It means defining the events that should reopen an assessment, such as expiring evidence, contract renewals, sub-processor or scope changes, incidents and ownership changes, then re-assessing only the vendors those events touch, at a depth set by their tier.</description>
      <enclosure url="https://procurecortex.com/covers/continuous-vendor-monitoring.jpg" type="image/jpeg" length="109012"/>
    </item>
  </channel>
</rss>
