Practice analysis · MFT
Dutch House of Representatives file transfer: what can this public source actually tell us?
Korper publicly announced a file-transfer platform for automated, secure and controlled exchange with third parties. The source does not publish realised outcomes — and that limitation is part of the analysis.
The MFT relevance is not a product name; it is the operating model. External parties, automated flows, security, auditability and recovery require more than an encrypted transfer protocol.
What the public project announcement actually states
- Korper announced in December 2018 that it had been selected to supply a new file-transfer platform for the Dutch House of Representatives.
- The announcement says the platform was intended to automate file exchange with third parties.
- The source explicitly describes the exchange as needing to be secure and controlled and refers to a tailored solution.
- The public source is a project announcement: it does not publish later results, SLAs, architecture details, product name or compliance outcome.
Third parties + automation + control are the real signals
The source is useful precisely because it contains few outcome claims. Three requirements are visible:
- exchange outside the organisation — third parties increase identity, protocol and change-management complexity;
- automation — flows should run predictably without manual hand-offs;
- secure and controlled operation — the organisation needs more than encrypted transport and must be able to evidence who exchanged what, when and with what result.
What would Boermans ask before choosing technology?
| Domain | Discovery question |
|---|---|
| Flow inventory | Which sources, destinations and third parties exist? |
| Identity | Which person or service identity may send and retrieve files? |
| Policy | Which data types may travel through which route? |
| Monitoring | When is a transfer technically and operationally successful? |
| Recovery | What happens after interruption, duplicate delivery or downstream failure? |
| Audit | Which timeline and evidence must be reconstructable later? |
| Continuity | Which flows are critical and which recovery objectives apply? |
Only after that comes the question of which MFT platform or architecture best supports these controls.
Why this page should not be called a success story
The source confirms an assignment and objectives, not a realised outcome. Boermans Digital therefore presents it as a project/source analysis, not as customer-result proof.
- No public KPIs or measured efficiency gains.
- No product/platform name is published in the announcement.
- No evidence about uptime, incident reduction or lead time.
- No claim that a particular regulation was automatically satisfied.
Assess MFT as an operating model, not only a protocol
An organisation can already use SFTP and still have an MFT problem. Once external partners, automation, auditability, recovery and controlled change become important, the key question moves from “is the connection encrypted?” to “can we govern the transfer service end to end?”
Sources and strength of evidence
The facts below come from the listed public source. The surrounding analysis is by Boermans Digital.
Boundary: This is an analysis of a public Korper project announcement, not evidence of later project outcomes and not a Boermans Digital customer case. Claims not present in the source are deliberately left unstated.