Little to explain.
A tool that can read every iFlow on a tenant has to explain itself to the security team. We built iFlowTailor so that the explanation is short: no server of ours, no credentials of its own, no writing out of the box. Everything else is on this page – every statement with a source.
- ArchitectureNo backend
No server, no telemetry, no remote configuration.1 Updates only through the browser stores, no remotely loaded code.
- AccessYour session
Read-only calls to a list of approved paths only2, with your existing SAP session and your roles.
- WritingOff by default
Validation chain, before/after, audit log3 – and can be blocked completely by policy.
- SecretsEncrypted
AES-GCM 256 with a non-exportable key4, only in the browser profile.
- LicenceOffline
Signed token, without a licence server5 and without usage tracking.
What the browser allows – and why.
This is also how it is stated in the store listings. Anything beyond the tenant is optional and requested per host.
| Permission | What for |
|---|---|
storage | Store settings, collections, tenant index and encrypted secrets locally |
sidePanel | Show the panel next to the iFlow editor (Chrome and Edge) |
| SAP Integration Suite hosts | Recognise the tenant and read with the existing session (*.hana.ondemand.com, *.cloud.sap) |
| Other hosts – optional | Only on request and per host: target APIs in the Test Studio, your AI endpoint, Confluence, vulnerability lookup |
| Remotely loaded code | None |
Only what you trigger. Only where you want it.
Every connection outside the tenant is triggered by you, needs the browser’s permission for exactly that host and is sent without cookies.
- Test Studio.The target API you enter; on-premise only through a relay iFlow with an allowlist6 that you import yourself.
- Ask Tailor.Your model, your key. Email addresses, hosts, URLs, IPs, IBANs, tokens, secrets, message IDs and your own terms7 are replaced before sending; the panel shows the text that is sent.
- Privacy guard.In the works, for all editions: finds email addresses, IBANs, card numbers, dates of birth and tax IDs8 before export and AI, and masks them.
- Vulnerability check.Only on request, only Maven coordinates and version9, with a preview before sending – to OSV.dev10.
- Confluence.Upload of the generated documentation after confirmation11; the token is stored encrypted in the browser.
IT rolls it out. The policy applies.
Extension, licence key and team policy come through the browser’s managed configuration12: Chrome and Edge via GPO or Intune, macOS via configuration profile, Firefox via policies.json. Users cannot change a policy distributed this way.
You put the policy together in Policy Studio13: enforce read-only, block individual write actions, allow AI or restrict it to specific endpoints, enforce masking, set a minimum score and a naming standard. Loaded from a file or URL, it only applies with a valid signature.
Plan the rollout with us →- Put the policy together. In Policy Studio, tested against a sample iFlow.
- Export. As JSON for the browser policy, with an expiry date.
- Roll out. Extension, licence and policy via Intune, GPO or Google Admin.
- Measure. Tenant Health14 and Security Risk Radar15 show whether the standard is working.
What is optional – and how it is built.
- Relay and Groovy Runner are optional.You import them yourself; iFlowTailor never imports or deploys anything automatically. The Runner16 is meant for development and test tenants and runs with a time limit on a copy of the message.
- Development.TypeScript in strict mode, more than 270 automated tests, CI on every push17, few runtime dependencies, lockfile.
- Tenant data never in the repository.Test data is anonymised. Please report vulnerabilities confidentially to security@iflowtailor.com.
Sources on this page
The superscript numbers in the text point here. Tap one to see the source right where it is used; all sources of this website are listed on one page.
- 1
No vendor server, no telemetry ↑Product · iFlowTailor product documentation, Security Whitepaper and the extension’s privacy policy · checked on 2026-11-04
- 2
Existing SAP session, no SAP password ↑Product · iFlowTailor product documentation, Architecture decision 0002 and Security Whitepaper, section 2 · checked on 2026-11-04
- 3
Read-only by default, writes only with a preview ↑Product · iFlowTailor product documentation, Security Whitepaper, section 2 · checked on 2026-11-04
- 4
Secrets encrypted locally ↑Product · iFlowTailor product documentation, Security Whitepaper, section 3 · checked on 2026-11-04
- 5
Licence verified offline ↑Product · iFlowTailor product documentation, Editions, technical section · checked on 2026-11-04
- 6
Test Studio and relay ↑Product · iFlowTailor product documentation, User guide, Test Studio; helper iFlows · checked on 2026-11-04
- 7
Ask Tailor with your own model and masking ↑Product · iFlowTailor product documentation, Security Whitepaper, section 4; AI providers and tasks · checked on 2026-11-04
- 8
Privacy guard (in the works) ↑Product · iFlowTailor product documentation, Changelog, “Unreleased” section, Privacy guard · checked on 2026-11-04
- 9
Vulnerability check ↑Product · iFlowTailor product documentation, Changelog 1.0.0, Vulnerability check · checked on 2026-11-04
- 10
OSV.dev – vulnerability database for open source ↑Vendor · OSV.dev (Open Source Vulnerabilities) · checked on 2026-11-04
- 11
Documentation generator ↑Product · iFlowTailor product documentation, User guide, Documentation · checked on 2026-11-04
- 12
Distribution via browser policy ↑Product · iFlowTailor product documentation, Enterprise rollout · checked on 2026-11-04
- 13
Team policies and custom rules ↑Product · iFlowTailor product documentation, Enterprise rollout and Security Whitepaper, section 5 · checked on 2026-11-04
- 14
Tenant Health, landscape and cleanup ↑Product · iFlowTailor product documentation, Editions, Team · checked on 2026-11-04
- 15
Security Risk Radar ↑Product · iFlowTailor product documentation, Changelog 1.0.0, Security Risk Radar · checked on 2026-11-04
- 16
Groovy Runner ↑Product · iFlowTailor product documentation, Changelog 1.0.0 and helper iFlows · checked on 2026-11-04
- 17
Development and supply chain ↑Product · iFlowTailor product documentation, Security Whitepaper, section 7 · checked on 2026-11-04
Questions about security.
- Can CloudDNA see my tenant data?
- No. There is no CloudDNA server in the data path, no telemetry and no analytics tool. Data only leaves the browser when you trigger it – for example to the API you call in the Test Studio, or to your own AI model.
- What permissions does the extension need on the tenant?
- None of its own. It uses the SAP session you are signed in with in your browser, and your roles. What you are not allowed to see, iFlowTailor cannot see either.
- Does iFlowTailor read private keys or passwords?
- No. From Security Material the extension reads alias, type, name and expiry date. Private keys, passwords and secure parameters stay untouched.
- Is there a security whitepaper and a security questionnaire?
- Yes. The whitepaper describes architecture, access, local data, external connections, policies and supply chain; we send a completed questionnaire on request. Write to security@iflowtailor.com or use the form.
- How do I report a vulnerability?
- Please report it confidentially to security@iflowtailor.com. We reply personally and, if you wish, credit you once the issue is fixed.
Your question isn’t here? Talk to me: +43 664 1964199 office@clouddna.at Demo on your tenant