FolioQ4AnswerLast checked 22 Nov 2026
As at
Sun 22 Nov 2026
Entries
7
Not yet
12
Page seal 5832, 060°26′. Drawn from the SHA 256 of this page’s source text5832
Page seal5832, 060°26′

How do I prove to a client that a security finding was fixed?

Short answer. Give the client a test they can rerun themselves. Record the exact check, the evidence it read, the result before and after, the date, and who checked it. Then take a fingerprint of the file and timestamp it with a public service, so any later change shows. A screenshot or a "done" email proves much less.

What we have measured. Our first four records were sealed on 22 Nov 2026: read only Stage A assessments of domains the founder owns, with no change applied, so none of them is a Proof of Fix yet. Record MSD 0001 can be checked in your browser.1

What a client actually needs to see

  1. What was wrong.

    The finding, in one sentence, with the evidence that showed it.

  2. What was changed.

    Each change, with the date and the person or tool that made it.

  3. The test.

    The exact command or check, written so anyone can run it again.

  4. Before and after.

    The test's output before the change and after it.

  5. Who checked.

    A second person or tool that did not make the change.

  6. Proof the record is unchanged.

    A fingerprint and a date that the client can confirm without trusting you.

Steps you can do yourself, free

  1. Pick a test that reads public facts, where you can.

    For domain and mail findings, a DNS query is ideal: anyone can rerun it. For example:

    nslookup -type=TXT _dmarc.clientdomain

    Microsoft's DMARC guide uses this same command to check a DMARC record.

  2. Run it before you change anything.

    Save the full output with the date and time, in UTC.

  3. Make the change, and log it.

    What, when, by whom.

  4. Run the identical test after.

    Save the output the same way. The client should see the difference in one glance.

  5. Ask a second person to rerun the test

    without your help, from their own machine. Note their name and the time.

  6. Put everything in one file

    (a PDF or a text file) and take its fingerprint. On Windows: certutil -hashfile report.pdf SHA256. On Mac or Linux: shasum -a 256 report.pdf. Send the fingerprint with the file.

  7. Timestamp the fingerprint.

    OpenTimestamps is free to use, with no sign up. Its own words: "A timestamp proves that some data existed prior to some point in time." If anyone later edits the file, its fingerprint will no longer match the timestamped one.

  8. Recheck later.

    A fix that holds for 30 days proves more than a fix on the day. Rerun the test after a month and add the result.

Mistakes that weaken the proof

  • A screenshot of a dashboard. The client cannot rerun it, and it can be edited.
  • "Fixed" with no test. The client has to trust you.
  • The same person making the change and checking it.
  • No date, or a date only on your own system.

How Marsadel does it

Every Marsadel job ends with a Proof of Fix record, numbered like MSD 0001. At launch every job runs in runbook mode: AI agents check the setup, write each step and test the result, and the client (or their agency) applies each change; we do not log in to client systems. The record lists each acceptance test with its result, the public evidence it read, the steps the AI agents wrote and the steps the client applied, a second AI model's verdict from a different vendor, and the name of the human reviewer who signed. The record is signed with our key and chained into our record log (the Register), and each day's summary is planned to be timestamped with OpenTimestamps and a public GitHub commit.2 The tests read public data, so the client, an insurer or a buyer of the business can rerun them. For mail units, the same tests run again at 30, 90 and 365 days after reject.

What is true today: the record log software is built and runs on our own machines. It chains and signs each event, rolls each day into one summary (a Merkle root) and has a command that checks the whole chain. No Proof of Fix record exists yet for any client, and nothing is anchored outside the firm.3 This site has been live on marsadel.com since 22 Nov 2026, in English; the public per record verify lookup and the roots and keys pages are not live yet.4, 5, 6

How to check one: How to check a record.

What it costs to have it done

The firm's source table holds no dated outside price for a signed fix record on its own.7

Marsadel's own price. The Proof of Fix record is not sold alone. It comes with every unit, at the unit's printed price. Examples, firm's own prices, Tier 1 list, US dollars, launch price first (you apply the changes) and full price in brackets: Mail Alignment 232 USD (290 USD), Domain and Mail Gap Closure 312 USD (390 USD), Certificate Automation for up to 20 hostnames 152 USD (190 USD), Domain Control Recovery 490 USD (no change to your systems either way, so one price). Agencies pay wholesale. Full list: price book.

Not on sale yet. The first unit opens after its quality test (target Sat 5 Dec 2026), once our company and checkout are live.

Not yet: each unit's Bench gate passed; the first, Unit 1 Stage A, targets Sat 5 Dec 2026, first sale Mon 7 Dec 20268, 9

Facts on this page

FactSourceRead
OpenTimestamps calendars free to use, no registration; "A timestamp proves that some data existed prior to some point in time."opentimestamps.org/ (S68)22 Nov 2026
nslookup -type=TXT _dmarc.domain checks a DMARC recordlearn.microsoft.com/en-us/defender-office-365/email-authentication-dmarc-configure22 Nov 2026
certutil -hashfile InFile [HashAlgorithm] generates a hash over a filelearn.microsoft.com/en-us/windows-server/administration/windows-commands/certutil22 Nov 2026
shasum -a 256 selects SHA256ss64.com/mac/shasum.html22 Nov 2026

Rows without an S number were read by the page writer and are not yet in the firm's source table.10

Questions people ask next

My client wants a pen test report. Is this the same? No. A pen test looks for new problems. A fix proof shows that one known problem is gone. Clients often need both.

Can the client check the fix without any tools? For public facts like DNS records, yes: an online DNS lookup site gives the same answer as the command above. For anything inside a network, they need someone they choose to rerun the test.

How long should I keep the evidence? As long as the contract or the client's auditor asks. Keep the fingerprint and timestamp with it, so the file can be checked years later.

What if the fix breaks later? The proof shows it was fixed on that date. A recheck shows whether it held. That is why a dated recheck at 30 days is worth adding.

If I order, do you train AI models on my data? No, unless you tick a consent box that allows it.


Written by AI agents and checked against the sources above. Last checked 22 Nov 2026. No named human has reviewed this page yet.11 No partner is signed in any country yet.12

Not yet in place12

Nothing is on sale yet; each numbered mark on this page points to a condition below. Every condition, with its state, is on the status board.

  1. 1first own property Proof of Fix records sealed in the Register, with n, labelled "client: the firm itself"
  2. 2signing key on the company; no daily summary anchored outside the firm yet
  3. 3first own run sealed
  4. 4public per record verify lookup, roots and keys pages live on marsadel.com
  5. 5second model vendor connected
  6. 6contracted human reviewers named
  7. 7dated outside prices for retest or remediation evidence services, with URL and read date
  8. 8each unit's Bench gate passed; the first, Unit 1 Stage A, targets Sat 5 Dec 2026, first sale Mon 7 Dec 2026
  9. 9company formed and checkout live
  10. 10each such row added to the plan source table with an S number and status
  11. 11named human reviewer under contract
  12. 12first partner agreements signed

Each item is also marked where it stands on this page.