<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Security on Ricky Moorhouse</title>
    <link>https://rickymoorhouse.uk/tags/security/</link>
    <description>Recent content in Security on Ricky Moorhouse</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Fri, 22 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://rickymoorhouse.uk/tags/security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Securing Sensitive Payload Logging in API Connect</title>
      <link>https://rickymoorhouse.uk/blog/2026/securing-sensitive-payload-logging-in-api-connect/</link>
      <pubDate>Fri, 22 May 2026 00:00:00 +0000</pubDate>
      <guid>https://rickymoorhouse.uk/blog/2026/securing-sensitive-payload-logging-in-api-connect/</guid>
      <description>&lt;p&gt;Unintentionally logging sensitive customer data (PII, financial info) is a major compliance risk. When deploying APIs, ensuring that this data is kept out of your logs requires robust, layered controls. Whilst developing APIs that will deal with this sensitive content you will often need to see what is being passed to ensure that everything is being handled as expected. Very often in a development or test environment you will be using a dummy payload to ensure the API is working as expected so it is key to ensure it is reflected at the different stages of processing as part of your test suites.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
