IPSRM Field: Security and data

IPSRM Field is a web app that keeps your assessments on your own device. This statement is for practitioners and for clients’ security teams.

What is stored, and where

- Your engagements, findings, evidence and photos are stored in the browser’s storage on your device, for IPSRM Field’s website only. They are not stored on any server, ours or anyone else’s.

- The app asks the browser to keep this data permanently. Settings › Storage and backups shows whether the browser has agreed. Without that, a browser may clear website data when the device is short of space, or after a period without use.

- Safari and an app added to the Home Screen keep separate storage, even on the same iPad. Work entered in one is not visible in the other.

- Settings, including your practitioner and firm details, the backup history, the licence and, if you hold one, the OIP licence, are stored on your device too. So are any estates you create in the Estate view: each estate’s name, the date it was created and the internal codes of its engagements. An estate holds no engagement data. An estate’s name is yours to choose, so it may include a client or site word. While a restore is under way, a short note of it is stored as well. The backup history and that note hold no client or site names.

- A re-assessment keeps its own copy of the sealed issue it was started from. Deleting the original engagement does not remove that copy. Delete the re-assessment as well to remove it.

What leaves the device

- No assessment data leaves the device. The app makes two kinds of outside request. It asks its own site, field.ipsrm.org, for its files and for the current version number, when it opens, when it comes back on screen, and when it installs or updates. These requests carry no assessment data. It also checks the licence with Gumroad: when you enter a licence key, about once a week afterwards, or when you tap Check licence now, IPSRM Field sends Gumroad the key, its product identifier and an instruction whether to count an activation. If you hold an OIP licence key, it is checked in the same way, and sends the same three things, when you enter it, about once a week afterwards, and when you tap Check OIP licence now. Nothing is sent for the OIP unless you hold an OIP key. No assessment data is sent. As with any web request, the hosting service and Gumroad also see the device’s IP address and the time, and Gumroad also sees the browser’s user agent and the app’s web address. Gumroad’s reply to each check, including the name and email on the purchase, is kept on the device only.

- The app’s security policy allows connections only to its own site and to api.gumroad.com. There are no analytics, no advertising, no cookies, no third-party scripts and no externally loaded fonts. The hosting service, Cloudflare, adds its own setting that can ask some browsers to report failed connections to the app’s site back to Cloudflare. A report holds the address requested, the type of error and network details, and no assessment data.

- Links to other websites, such as the framework references on npsa.gov.uk and securedbydesign.com, and pages on ipsrm.org, open only when you tap them. No referrer is passed on, and the app fetches nothing from them.

- Backups, reports and exports leave the device only when you save them and choose where they go.

Backups

- Only IPSRM Field’s own backups are a dependable way to keep your work so that it can be restored into IPSRM Field. Your device’s own backups (iCloud, or a backup to a computer) may not include browser storage, so do not rely on them. “Export everything for keeping” (Settings › Storage and backups) adds a lasting copy of every engagement that opens without IPSRM Field; it cannot be restored into the app.

- A backup can be protected with a passphrase of at least 12 characters. Its whole contents, photos included, are then encrypted (AES-GCM, 256-bit, with the key derived from the passphrase by PBKDF2-SHA-256, at least 600,000 iterations). The passphrase is never stored and cannot be recovered.

- Export everything for keeping (Settings › Storage and backups) saves every engagement in one file that opens without IPSRM Field. Engagements with a protective marking go inside an encrypted ZIP file (AES-256) that opens in 7-Zip. Other programs that read the WinZip AES format should also open it, but only 7-Zip has been tested. Its passphrase, of at least 12 characters, is protected less strongly than a backup’s: the ZIP format sets 1,000 rounds of key-stretching (PBKDF2-SHA-1), against 600,000 for a backup (PBKDF2-SHA-256), so a guessed passphrase can be tried much faster. Use a long passphrase of several words.

- When an engagement carries a protective marking, its backups and exports of original photos must be protected, and Export everything puts it inside the encrypted ZIP. On a protected backup or export of original photos, the marking is shown on the outside of the file, so its handling requirement is visible before it is opened, and the file name never includes the organisation or site. When a protected backup is restored, IPSRM Field checks the marking on its outside against the engagement’s own marking inside. If they differ, the engagement is restored with its own marking, and you are told. On an export of original photos, the outside marking is a handling aid only: it is not checked against anything when the export is opened. The export’s encrypted ZIP shows no marking on the outside; inside it, engagements are in folders named engagement-01 and so on, and nothing that identifies a protected engagement appears outside it.

- An estate backup is a separate file that holds the estates only (their names, dates and which engagements each groups), never engagement data. It can be protected with a passphrase in the same way as an engagement backup, and it must be protected when an estate includes an engagement that carries a protective marking, or whose baseline does, or when the app lock is on. Like a protected engagement backup, it shows a protective marking on its outside when any engagement in the estates carries one, so its handling requirement is visible before the file is opened. Where the markings differ, you choose among those present. The marking is a handling label only: it is shown when you restore, but not checked. It can be saved from the Estate view or from Settings › Storage and backups, at any time, including after an OIP licence has ended. Your engagements are still backed up separately.

- Export everything for keeping also includes estates.csv, a list of the estate names and which engagements each groups. It goes inside the encrypted ZIP whenever the export is encrypted. Otherwise it is a plain file.

The app lock (optional)

- With the app lock switched on in Settings, every engagement and photo, and every estate, is stored encrypted on your device, and IPSRM Field asks for your passphrase when it opens, after a period without use, and when you tap Lock.

- The licence, and the OIP licence if you hold one, stay readable so the licence check still works. They hold no assessment data.

- A forgotten passphrase cannot be recovered: there is no server that could. The only way forward is to erase the device’s data and restore from backups.

Reports

- Word reports, the Excel register and PDFs saved from Word are not encrypted. Store and send them as the engagement’s protective marking and your client’s requirements demand. The marking prints on every page of the report and every sheet of the register. The Estate Summary, the one-page Word report made from the Estate view, is a report in the same sense: it is not encrypted and cannot be protected with a passphrase. Its marking is the one its engagements carry. Where they differ, you choose among the markings present, and it is never “None” if any of them is marked. It prints on every page.

- A sealed issue carries a verification code. Entering the code in IPSRM Field, on a device that holds the engagement or a re-assessment started from it, shows the sealed record of findings, scores, tiers, the Overall Exposure Position and the methodology edition, and the Framework Cross-Reference appendix when the report included it, so those figures in any copy of the report can be checked against it.

Photos and dictation

- Photo location is off by default for each engagement. When it is on, the location is kept in the evidence record only and never appears in report images. Photos chosen from your Photos library keep the details they carry, so the original may include where it was taken; working copies and report images never include location.

- On sensitive sites, take photos with the app’s camera rather than choosing them from the Photos library.

- You can dictate into any text box using your device’s keyboard microphone. Dictation is provided by your device’s keyboard, not by IPSRM Field. Depending on the device, language and settings, it may be processed on the device or by the device maker’s servers. Check your device’s dictation settings before using it on sensitive sites.

On the device: what you are responsible for

- Protect the device with a passcode and a short Auto-Lock time.

- Keep the device’s operating system and browser up to date.

- The iPad’s app switcher may show the last screen you viewed. On sensitive sites, switch on the privacy screen, which keeps your work out of the app switcher once it has covered the screen, and close IPSRM Field from the app switcher before leaving the iPad unattended.

- Keep current backups of every engagement, stored as your client’s requirements demand.

- Before handing a device on, use Settings › Storage and backups › Erase this device. It also removes any estates. Your licences, the IPSRM Field licence and the OIP licence, are removed only if you tick “Also remove the licence from this device”.

The code and the accounts behind it

- Hosted on Cloudflare Pages, with no server-side code. The code is held in a private GitHub repository; it is published only from a protected release branch, after release checks. Settings › About this version shows the exact version and its code reference.

- The accounts behind the app (code, hosting, sales and email) are protected with two-factor authentication.

Tested on

Tested on iPad and iPhone (iPadOS 26.6.1 and iOS 26.6.2, Safari and the Home Screen app), on Mac (macOS 10.15.8, Safari 15.6.1) and on Windows 11 (version 25H2) with Edge and Google Chrome. Android has been tested in an Android emulator; a real-device test is pending.

Questions

Questions, or to report a security concern: support@ipsrm.org.

Vulnerability disclosure policy

Vertex Method wants to hear about security problems in IPSRM Field. We welcome good-faith reports and will respond to them.

Scope

The IPSRM Field app at field.ipsrm.org and the files it serves.

Out of scope

Third-party services such as Gumroad, Cloudflare, IONOS and Squarespace. Social engineering of our staff or customers. Denial of service. Physical attacks. Findings that depend on an unlocked or already compromised device.

How to report

Email support@ipsrm.org, which is also the contact in our security.txt file at field.ipsrm.org/.well-known/security.txt. Please include:

- what you found and where

- the steps to reproduce it

- the browser, device and app version you used

- any evidence, such as screenshots

What we will do

- Acknowledge your report within 5 working days.

- Give you a first assessment within 10 working days.

- Keep you informed until it is fixed.

- Credit you in our acknowledgements if you wish. We do not pay rewards.

What we ask of you

- Test only your own copy of the app, with your own data or the Ardmore demo.

- Do not access, change or delete anyone else’s data, and do not use real customers’ licence keys.

- Do not disrupt the service or run automated attacks at volume.

- Give us 90 days to fix the problem before you publish details. We will agree a different period with you if needed.

Good faith

If you follow these rules, we will not take legal action against you for your research.

Vertex Method Ltd is registered with the ICO at Reference ZC291692.

Last reviewed 08 November 2026.