Evidence behind each item
Where a status applies, the table marks each item tested, documented or not yet. The architecture page gives the same status for each security claim.
Trust center. Security. Data handling.
Sylox’s ISO/IEC 27001 certification is in progress and it holds no SOC 2 report yet. The table is dated November 7, 2026 and says how to get the security pack.
Where a status applies, the table marks each item tested, documented or not yet. The architecture page gives the same status for each security claim.
IRIS can be deployed in your own infrastructure, on-premises or in any cloud, so your data stays within your environment. Sylox-hosted environments are used only for demos and agreed pilots.
Outbound hosts with port and purpose, the grants for each source type and the read-only setup, for your firewall team and auditor. Sent on request.
Report a suspected vulnerability in IRIS or this website to security@syloxiris.com. Our security contact is also published in our security.txt file.
IRIS findings can support your own ISO/IEC 27001 or SOC 2 audit as evidence, and your auditor decides what they prove. For ISO/IEC 27001:2022, Annex A 5.9 (inventory) and 5.12 (classification) are the closest controls. The ISO/IEC 27001 evidence page maps the rest, and the SOC 2 evidence page covers SOC 2. IRIS maps its evidence to ISO/IEC 27001 and SOC 2 controls through its unified compliance framework. A scored readiness view for either isn’t in v1; ask us if you need one.
IRIS evidence is not a certification and not a guarantee of compliance. It shows where you stand and what to fix next.
To check our side of a review, start with the architecture page. It shows when each connection fires and what it carries, with a flow-log query your team can run against a test scan.
Status on November 7, 2026, for IRIS v1. Evidence: tested, documented (read in IRIS v1, not independently tested) or not yet. Capabilities vary by edition.
| Item | Status | Notes | Evidence |
|---|---|---|---|
| SOC 2 report | Not held | Not started. | Not yet |
| ISO/IEC 27001 certification | In progress | Sylox’s ISO/IEC 27001 certification is in progress; Sylox is not certified yet. No audit date is published. | Not yet |
| Penetration test | No report yet | A third-party penetration-testing firm, which is also a Sylox partner, will run the test and issue the report. | Not yet |
| Security pack | On request | Hosts, ports, grants per source type and read-only setup. Ask through the contact page. | n/a |
| Customer data location | Customer-hosted by default | Findings, coverage records and stored samples stay on your host, unless you turn on emailed reports. | Documented |
| Outbound connections | Listed by kind | License service, sources you scan, a time source; emailed reports and AWS Systems Manager if you use them. | Tested in part: our packet capture of November 2, 2026 had no Microsoft 365 scan |
| Source access | Read access | IRIS reads through accounts you create. Some credentials, such as an Azure storage key, can also write; see the pack. | Documented |
| Source credentials | Credentials encrypted at rest | Inside your deployment. Where the key is kept and how it rotates are in the pack. | Documented |
| Sign-in | OIDC and SCIM | OIDC single sign-on and SCIM provisioning in editions that include them; passwords stored hashed. No SAML today. | Documented |
| User roles | Predefined roles | Custom roles are not available today. | Documented |
| Transport | TLS 1.2 or later | Between browsers and the bundled HTTPS edge. Whether a source connection requires TLS varies by source type. | Documented |
| Platform audit trail | In place | Records IRIS activity, such as adding a source; we claim no tamper resistance. Exportable in data-export editions. | Documented |
| Sample storage | Configurable | Stored samples are masked by default for personal-data columns; you can set all to masked, or off. | Documented |
| Findings retention | Set by you | Findings stay in your IRIS database until you delete them; an administrator sets audit-trail retention. | Documented |
| Releases | Checksum-verified bundles | Installer checks a checksum manifest; images are pinned by digest; no run-time updates. Bundles aren’t signed today. | Documented |
| Support access | Granted by you | IRIS keeps no standing connection to Sylox, so any support access starts on your side. | Documented |
| Support location | India and the United States | Sylox operates from India and the United States; the license service runs in India. | n/a |
While IRIS runs on your host, it reaches the license service at activation and when an admin validates. It also reaches the cloud and SaaS sources you choose, during their scans. The host syncs its clock with a time source, which can be your own, and install-time connections are listed in the security pack.
After a one-time license activation, IRIS can run in isolated and air-gapped networks for sources inside your network. Microsoft 365 and other SaaS sources need access to those services.
During a scan, IRIS reads values in memory. It keeps findings, coverage records and stored samples in the database on your host. Scans run only when your team starts one or on the schedule you set.
See how a scan runsNot yet. This page sets out our security program, and we answer your security questionnaire during scoping.
Classification uses pattern rules, checksums and local name recognition inside your deployment. IRIS sends no customer data to external AI services. Explore AI governance
Yes. We sign a data processing agreement with each customer, and the current sub-processor list is available on request from privacy@syloxiris.com.
Email security@syloxiris.com with the affected URL or component, the likely impact and the steps to reproduce it. Don’t access data that isn’t yours, or test a customer’s IRIS install without its written permission.
Send your security questionnaire with your request for the security pack, and we’ll answer both during scoping.