Security
Technology is useful when you can trust it.
Last updated:
16 October 2026
WeAreBrain Agency Group BV · Chamber of Commerce 73256560 · VAT NL859424133.B01 · DUNS 492850103
Laan der Hesperiden 166, 1076 DX Amsterdam, The Netherlands
security@wearebrain.com
Security applies across the WAB ecosystem, but the exact controls depend on the product, hosting model, client environment and contract. This page describes our general approach; project-specific security documentation defines the actual setup for a given deployment.
Security starts with architecture
WAB systems can connect to company data, internal tools and business processes. We therefore consider access, data boundaries, deployment, logging and failure modes from the start rather than treating security as a final review step.
Protecting data
We use technical and organisational measures designed to protect data when it is stored and when it moves between systems. Depending on the engagement, we can support dedicated environments, private cloud deployments, customer-controlled infrastructure and separated data stores.
Where we host or operate separate customer environments, we design for logical or physical separation appropriate to the architecture.
Identity and permissions
Access should follow clear rules and the principle of least privilege. Depending on the deployment, controls can include role-based access, managed identities, restricted service permissions, single sign-on and customer-controlled identity providers. Where supported, clients may also retain control over encryption keys.
Agents, tools and code execution
AI systems increasingly call APIs, query databases and trigger workflows. That makes tool access and execution boundaries important. WAB / Sinas and related deployments can be configured with limits around identity, network access, runtime, tools and approval steps so an agent only gets the capabilities it needs.
Development and operations
Our engineering practices can include code review, dependency scanning, vulnerability monitoring, environment separation, secrets management, logging and security testing. The exact controls and assurance level depend on the product and engagement.
Incidents
If we identify a security issue that affects a client or service, we follow our incident-response process and work with the affected parties to investigate, contain and resolve it. Contractual notification commitments, where applicable, are set out in the relevant agreement.
Responsible disclosure
If you believe you have found a security vulnerability in a WeAreBrain or WAB product, please report it to security@wearebrain.com. Please avoid accessing, changing, destroying or sharing data that does not belong to you, and give us a reasonable opportunity to investigate before publishing details.
Security reviews
We are used to discussing architecture, deployment, access controls, data handling and security requirements with client security, legal and procurement teams. Evidence and questionnaires are handled in the context of the relevant product or engagement.
Contact
Security questions and vulnerability reports: security@wearebrain.com.




