Last updated: 16 November 2026
Aegis Vision builds software that schools rely on for safety. We want to hear about security weaknesses before anyone else finds them, and we will treat people who report them in good faith as partners, not adversaries. This policy follows the structure recommended by RFC 9116, and the sites publish a security.txt file at /.well-known/security.txt that points here.
1. Scope
In scope without prior arrangement
- The public websites at aegisvision.net, aegisvision.ae and aegisvision.org, including the contact form and the
wwwand apex hosts. - Email and DNS configuration for those domains (for example SPF, DKIM, DMARC and DNSSEC findings).
In scope by arrangement only
- The Aegis Vision product software (the on-site detection agent, the guard console and the operator hub). This software runs on customers' own servers and private networks, so testing it without agreement would affect a customer. If you want to assess it, write to security@aegisvision.org first and we will discuss a test environment and written terms.
Out of scope
- Denial-of-service testing of any kind, including resource exhaustion and volumetric attacks.
- Social engineering of our staff, customers, suppliers or their staff (phishing, pretexting, vishing).
- Physical attacks on our premises, or on any school or customer site.
- Third-party services we use but do not control, including our hosting provider, mail provider and DNS registrar; report those to the provider under its own policy.
- Customer deployments and customer networks, unless the customer and we have both agreed in writing.
- Findings that require a stolen or borrowed device, a compromised account, or physical access.
- Reports about missing best-practice headers, version banners or similar with no demonstrated impact; we will still read them, but they are low priority.
2. Safe harbour
If you make a good-faith effort to follow this policy, we will:
- not pursue or support legal action against you for your research, and
- work with you to understand and fix the issue quickly.
"Good faith" means that you only test systems in scope, you stop and tell us as soon as you encounter personal data, customer data, credentials or any sign that a system is in live use by a school, you do not copy, alter or delete data beyond the minimum needed to demonstrate the issue, you do not disrupt service, you do not exploit an issue beyond proof of concept, and you keep the details confidential until we have fixed it or the disclosure window has passed.
We cannot authorise testing of systems we do not own, and this policy does not bind third parties, law-enforcement agencies or courts. If a third party raises a legal matter about research done in line with this policy, we will make it known that the research was authorised.
3. How to report
Email security@aegisvision.org.
PGP: no key is offered at present. If you need an encrypted channel, say so in a first email and we will arrange one.
If you prefer not to send details by email until a key is available, send a short message first and we will arrange a secure channel.
You may report anonymously. If you do, we cannot update you on progress.
4. What to include
- Which system is affected (URL, host, or product component and version).
- The type of issue and its impact as you understand it.
- Step-by-step instructions to reproduce it, with requests, responses, screenshots or a short video where helpful.
- Any proof-of-concept code, kept to the minimum needed.
- Whether you have found, accessed or stored any personal or customer data in the course of the research (please delete it once we confirm receipt).
- How you would like to be credited, if at all.
5. What we will do
| Step | Target |
|---|---|
| Acknowledge your report | Within 3 working days (UAE working week) |
| Give a first assessment and status | Within 10 working days |
| Keep you informed of progress | At least every 30 days until the issue is resolved |
| Fix or mitigate | As quickly as the severity warrants; we will tell you our planned timeline |
We will tell you when the issue is fixed and, with your agreement, credit you on our acknowledgements page.
6. Coordinated disclosure
We ask that you give us 90 days from the date of your report before you publish any details. If we fix the issue earlier, you may publish once we confirm the fix is deployed. If we need longer than 90 days, for example because a fix must be rolled out to on-site servers at several schools, we will explain why and agree a new date with you. We will not ask you to stay silent indefinitely.
For issues in the product software that affect live school deployments, we may ask for extra time because updates reach each site through the site's own maintenance process and some sites are offline by design.
7. Rewards
We do not run a bug bounty programme at present and we do not pay for reports. We will say thank you, credit you if you wish, and keep you informed. If this changes, this page changes first.
8. Things we ask you not to do
- Do not access, download or modify data that belongs to anyone else. If you hit personal data by accident, stop, record only what is needed to show the issue, and tell us.
- Do not run automated scanners against the sites at a rate that could degrade them.
- Do not attempt to reach any school's network, cameras or guard console. Those are not ours to authorise.
- Do not demand payment as a condition of disclosure.
9. Contact
Security: security@aegisvision.org
General: help@aegisvision.org
Policy page: /security/disclosure
Machine-readable: /.well-known/security.txt