<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Daniel Nsumba on Medium]]></title>
        <description><![CDATA[Stories by Daniel Nsumba on Medium]]></description>
        <link>https://medium.com/@nsumbadaniel589?source=rss-30855c846459------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*HXcRZuFVLgAjVqi3</url>
            <title>Stories by Daniel Nsumba on Medium</title>
            <link>https://medium.com/@nsumbadaniel589?source=rss-30855c846459------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 08:01:37 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nsumbadaniel589/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Quiet Death of SFTP — And Why Your Supplier Contracts Should Have Predicted It]]></title>
            <link>https://medium.com/@nsumbadaniel589/the-quiet-death-of-sftp-and-why-your-supplier-contracts-should-have-predicted-it-4ac2b789c2fc?source=rss-30855c846459------2</link>
            <guid isPermaLink="false">https://medium.com/p/4ac2b789c2fc</guid>
            <category><![CDATA[iso-27001-certification]]></category>
            <category><![CDATA[iso-27001-standard]]></category>
            <category><![CDATA[grc]]></category>
            <category><![CDATA[iso-27001]]></category>
            <category><![CDATA[sftp]]></category>
            <dc:creator><![CDATA[Daniel Nsumba]]></dc:creator>
            <pubDate>Mon, 01 Jun 2026 17:34:19 GMT</pubDate>
            <atom:updated>2026-06-01T17:34:19.773Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sfvswLSGIWtJV697iueeEQ.jpeg" /></figure><h3>What replacing a file transfer protocol actually reveals about an organization’s information security maturity</h3><p>This week, a question came across my desk that on the surface looked simply: a client wants to replace SFTP with something more modern. Could we suggest options?</p><p>That’s the question. Here’s the conversation it actually started.</p><p>Because file transfer is rarely “just” file transfer. Especially in regulated industries, every file moving between two organizations carries an entire chain of accountability behind it — POPIA obligations, supplier agreements, encryption standards, retention rules, audit expectations, breach notification timelines, and the contractual web that ties one company’s security posture to another’s.</p><p>And the technology question SFTP vs cloud storage vs MFT vs API — turns out to be the smallest part of the answer.</p><h4>The technology question — quickly</h4><p>For the record, here’s the short version of the technical landscape.</p><p><strong>SFTP is mature, secure, universally supported.</strong> It’s not going away. But for new architecture, it’s increasingly being replaced by:</p><ul><li><strong>Cloud object storage</strong> (Azure Blob, AWS S3, Google Cloud Storage) with API access, pre-signed URLs, and IAM-based authorisation</li><li><strong>Managed File Transfer (MFT) platforms</strong> like Cleo, GoAnywhere, and Axway — purpose-built for governed B2B exchange with native audit and compliance reporting</li><li><strong>HTTPS REST APIs</strong> with mutual TLS or OAuth tokens, for organisations with strong engineering teams who want event-driven integration</li><li><strong>Cloud-native managed SFTP</strong> (AWS Transfer Family, Azure SFTP for Blob) — keeps the SFTP interface for legacy automation while modernising the back-end governance</li></ul><p>Each has its place. Each is “modern” in its own way. Each can be ISO 27001 compliant, or not, depending on how you implement it.</p><p>But none of that is what makes the conversation interesting.</p><h4>What the conversation actually reveals</h4><p>When two organisations sit down to replace SFTP between them, here’s what they end up surfacing:</p><p><strong>1. Is there even a current data flow diagram?</strong></p><p>In half the cases I’ve encountered, the answer is no. SFTP was set up years ago, documented in a runbook somewhere, and the people who configured it have moved on. The data flow is alive but uncharted.</p><p>You cannot secure what you cannot describe. The first artefact of any file transfer modernisation should be a clean data flow diagram — endpoints, encryption, retention, owners. That alone is half the work.</p><p><strong>2. What’s the data classification, really?</strong></p><p>“Just a CSV” is almost never just a CSV. In regulated sectors, it’s likely to contain personal information, health data, financial information, or a combination of all three. Each carries different obligations.</p><p>POPIA treats health information as special category data with the highest protection requirements. A “let’s just keep using SFTP because it’s encrypted” approach misses the broader controls that apply regardless of protocol — retention, access governance, breach notification, data residency.</p><p><strong>3. Whose contract is this anyway?</strong></p><p>This is the one most teams stumble on. When organisation A sends a file to organisation B, who is the responsible party under POPIA? Who’s the operator? Are there sub-operators? What does the contract say about minimum security measures? What does the contract say about breach notification timelines?</p><p>Replacing the protocol is meaningless if the underlying supplier agreement doesn’t reflect the new architecture. ISO/IEC 27001 control A.5.19–22 (supplier relationships) doesn’t care which protocol you chose. It cares whether the agreement defines responsibilities, sets expectations, and allows for audit and review.</p><p><strong>4. Where will the data physically sit?</strong></p><p>Moving to cloud object storage answers many technical questions and raises one new one immediately: where is the data hosted? POPIA cross-border transfer requirements apply. So do your customer’s customer’s expectations, often baked into upstream contracts you haven’t read.</p><p>If you’re in South Africa and your storage region is in Ireland or Virginia, that’s a decision that needs documenting, justifying, and contractually permitted. It’s not a deal-breaker — adequate protection frameworks exist — but it is a question that has to be answered explicitly.</p><p><strong>5. Who holds the encryption keys?</strong></p><p>Modern cloud platforms encrypt at rest by default. But “encrypted” can mean three very different things:</p><ul><li>Provider-managed keys (lowest control, simplest operation)</li><li>Customer-managed keys via the provider’s KMS (better control, audit trail)</li><li>Customer-supplied keys (highest control, you literally hold the keys)</li></ul><p>For data you don’t fully own — files exchanged between organisations on behalf of someone’s customers — customer-managed or customer-supplied keys are increasingly the expected standard. Not because the provider can’t be trusted, but because key holding is the cleanest way to demonstrate that <em>you</em> control access, not the provider.</p><p>This is the kind of design detail that quietly separates organisations that pass demanding audits from those that don’t.</p><h4>The bigger pattern</h4><p>What I’ve seen, again and again, is that the protocol upgrade is the visible part of a much larger maturity question. Organisations that replace SFTP and end up with cleaner governance are the ones who used the change as an excuse to:</p><ul><li>Refresh data flow documentation</li><li>Re-classify the data being exchanged</li><li>Update the supplier agreement</li><li>Define encryption and key management policy</li><li>Map controls to ISO/IEC 27001 Annex A</li><li>Confirm audit, retention, and breach notification responsibilities</li></ul><p>Organisations that just swap SFTP for a cloud bucket and consider the job done end up with all the same governance gaps they had before, just hidden behind newer technology.</p><p>The protocol is the smallest decision. The governance around it is the actual work.</p><h4>The practical question for your week</h4><p>If you’re sitting in a similar conversation — a client asking you to “move off SFTP” — try this as the first question back:</p><p><em>“Before we choose a replacement, can we look at the current data flow, the supplier agreement, and the data classification together? The technology choice becomes much clearer once we know what we’re actually protecting.”</em></p><p>Nine times out of ten, the answer will be “we haven’t looked at those for a while.”</p><p>That’s where the value of the work actually sits. Not in choosing between Azure Blob and Cleo and S3. In using the protocol change as a forcing function to bring the governance up to where it should already be.</p><h4>Closing thought</h4><p>ISO 27001 is sometimes accused of being too process-heavy, too paper-heavy, too detached from the technical work. But moments like this — a simple “let’s replace SFTP” question — are exactly where the value of the standard shows itself.</p><p>It’s not the certificate on the wall. It’s the discipline of asking, every time the architecture changes, whether the controls still hold. Whether the contract still reflects the reality. Whether the audit trail still tells the story.</p><p>The protocol will change again in five years. The discipline of asking the right questions is what stays useful.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ac2b789c2fc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[IS0 27001 — The Day Our Auditor Asked About a Policy We Hadn’t Written Yet]]></title>
            <link>https://medium.com/@nsumbadaniel589/is0-27001-the-day-our-auditor-asked-about-a-policy-we-hadnt-written-yet-d61b69f26230?source=rss-30855c846459------2</link>
            <guid isPermaLink="false">https://medium.com/p/d61b69f26230</guid>
            <category><![CDATA[iso-27001]]></category>
            <category><![CDATA[iso27001implementation]]></category>
            <category><![CDATA[iso-27001-certification]]></category>
            <category><![CDATA[grc]]></category>
            <dc:creator><![CDATA[Daniel Nsumba]]></dc:creator>
            <pubDate>Thu, 21 May 2026 20:51:06 GMT</pubDate>
            <atom:updated>2026-05-21T20:53:22.230Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Lessons from contributing to an ISO 27001 certification — and why governance is harder than detection</strong></h3><p>Our external audit was three days in.</p><p>The auditor — patient, methodical, polite in the way that auditors are when they’re about to find something — flipped to a page in our policy library and asked:</p><p><em>“Where’s your control on secure development lifecycle for third-party code? Annex A.8.28?”</em></p><p>I knew the answer. We had it. Two months earlier I’d drafted it, mapped it to the right control objective, and circulated it to the dev team for input. What I didn’t have, in that moment, was the <strong>evidence</strong> that we’d been applying it.</p><p>The policy existed. The practice was partially there. The link between the two — the audit trail — was the gap.</p><p>That was the day I learned what governance actually is.</p><h4>Governance isn’t writing policies. It’s making them visible.</h4><p>Before that audit, I thought policies were the work. Write the policy, get it signed off, file it in SharePoint, move on.</p><p>ISO 27001 doesn’t care about your policy library. It cares about whether your policy library <strong>drives behavior</strong> that auditors can see.</p><p>That distinction is the whole game.</p><p>A SOC analyst can detect a sophisticated threat in 30 minutes. A governance professional can spend three months making sure the SOC’s incident response runbook is documented, tested, signed off by the right stakeholders, version-controlled, and reviewed annually — so that when the auditor asks, “show me how you handle an incident,” the answer isn’t “we just do it.”</p><p>One job is reactive. The other is structural. Both are needed. Neither is more important than the other.</p><h4>Three things I wish I’d known earlier</h4><p><strong>1. Evidence beats elegance.</strong></p><p>A 40-page polished policy that no one references is worth less than a 2-page policy with attached evidence of quarterly application. Auditors aren’t grading your prose. They’re grading whether the policy lives in the operational rhythm of the business.</p><p>For every policy you write, ask one question: <strong>what evidence will exist three months from now that this policy is being followed?</strong></p><p>If the answer is “I don’t know” — your policy is decoration, not control.</p><p><strong>2. Stakeholder buy-in is half the job.</strong></p><p>The hardest part of ISMS work isn’t drafting controls. It’s getting the dev team, the customer support team, the HR team, and the finance team to agree that the controls apply to them too.</p><p>Security is one of the few corporate functions where everyone thinks “that’s IT’s job.” Until ISO 27001 makes it explicit that change management, supplier risk, awareness training, and asset registers are everyone’s job.</p><p>You don’t win this by being the rule enforcer. You win it by being the person who makes compliance easier for the rest of the business — templates, walkthroughs, pre-filled forms, plain-English explanations of why something matters.</p><p><strong>3. Maintenance is where most ISMSs die.</strong></p><p>Companies celebrate the day they get certified. Three months later, the policies are stale, the risk register hasn’t been updated, the management review meeting was postponed twice, and nobody remembers when the last internal audit happened.</p><p>ISO 27001 surveillance audits exist because ISMSs decay without active maintenance. Calendar-driven cadences, owned tasks, and ruthless prioritisation are what separate organisations that hold certification for years from those that lose it after the first surveillance cycle.</p><p>In my experience, this is where most security professionals quietly disengage — the implementation was exciting, the maintenance is repetitive. But the maintenance is where the actual security culture gets built.</p><h4>What this looks like in practice</h4><p>A real example from my current role at a financial services SaaS provider.</p><p>When a banking client sent us their annual due-diligence questionnaire, the volume of questions had grown by about 30% year-on-year. New questions about AI vendor risk, third-party SBOMs, post-quantum cryptography readiness, and supply chain security.</p><p>Three years ago we might have scrambled to answer these. With a maintained ISMS:</p><ul><li>The supplier risk register already covered AI vendors</li><li>The asset register already classified AI tools alongside other software</li><li>The vulnerability management programme already tracked dependencies in our supply chain</li><li>The annual risk assessment already captured emerging threats</li></ul><p>We answered the questionnaire in four working days. Two of those were spent waiting for a colleague to come back from leave.</p><p>That wasn’t because we’re geniuses. It was because the ISMS was alive — the controls were maintained, the evidence was current, and the policies meant something to the people executing them.</p><p>That’s the moment ISO 27001 stops feeling like compliance overhead and starts feeling like a competitive advantage.</p><h4>The skill set that matters</h4><p>If you’re earlier in your career and wondering whether to go deeper into technical security or into GRC, here’s the honest answer: <strong>both, eventually.</strong></p><p>The strongest information security professionals I’ve worked with — including consultants, auditors, and CISOs — combine:</p><ul><li>Technical depth (so they understand what the controls are actually protecting)</li><li>Framework fluency (so they can map technical reality to certifiable structure)</li><li>Communication clarity (so they can translate between engineers, lawyers, executives, and regulators)</li><li>Audit empathy (so they design controls that are operable, not just documented)</li></ul><p>You can start anywhere. The mistake is staying in one lane forever.</p><p>A pen tester who learns ISO 27001 becomes invaluable to a consultancy. A policy writer who learns Linux internals becomes a CISO candidate. The doors open in both directions.</p><h4>Closing thought</h4><p>The auditor who asked about Annex A.8.28 didn’t catch us off guard because we didn’t know the answer. They caught us off guard because we hadn’t thought about evidence the same way they had.</p><p>We closed that audit successfully. We tightened our evidence practices. The next surveillance cycle went smoother.</p><p>But the lesson stays with me: governance isn’t the absence of work. It’s a different kind of work — slower, less visible, more structural — that determines whether the rest of your security operation has anywhere stable to stand.</p><p>If you’re working in this space, especially in regulated industries, I’d love to hear what’s worked for you. What’s the one ISMS practice that genuinely changed your organisation’s posture?</p><p>Daniel Nsumba is a Security Operations Analyst contributing to ISO 27001:2022 ISMS implementation and maintenance at a financial services SaaS provider in Johannesburg.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d61b69f26230" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>