Report to: info@qcramai.com, or
the
contact form. Put
Security in the subject line so it reaches the right people
quickly. We acknowledge reports within
3 business days.
1. What is in scope
Systems Qcramai owns and operates:
- qcramai.com and its subdomains;
- the Free Web Scan, the performance and container scanners, and the free security
tools hosted on this site;
- our products, Vexia IQ and Vendor Attest;
- DNS and email-authentication configuration for our own domains.
2. What is out of scope
Client systems are out of scope. We test other organizations’
systems under a written, documented authorization. If you have found a weakness in a
system one of our clients owns, report it to that organization. We cannot authorize
testing of a system we do not own, and we cannot pass your report on for you.
Also out of scope on our own systems:
- third-party services we merely consume — our CDN, analytics and
mail providers. Report those to the provider;
- raw scanner output with no demonstrated impact;
- missing hardening headers, cookie flags, TLS cipher preferences, SPF/DMARC strength
and similar configuration opinions, unless you can show a concrete exploit path;
- rate-limiting and resource-exhaustion issues reachable only by volume;
- social engineering, phishing, or anything aimed at our staff or offices;
- self-XSS, clickjacking on pages with no sensitive action, and issues that need a
rooted device, a long-unsupported browser, or a man-in-the-middle position.
3. Rules of engagement
Stay within what it takes to demonstrate the problem:
- no denial-of-service or load testing against our infrastructure;
- no automated fuzzing or mass scanning at a rate that degrades the service for
others;
- stop at the first proof — do not pivot, escalate privileges, or enumerate
further;
- do not access, modify, exfiltrate or keep data that is not yours. If you reach
someone else’s data by accident, stop, tell us, and delete your copy;
- use your own test accounts and test data, never a real customer’s;
- give us a reasonable period to fix the issue before publishing anything about it.
4. What to include in a report
A report we can act on usually has:
- the exact URL, endpoint or host affected;
- step-by-step reproduction instructions, with the request and response where they
matter;
- what an attacker gains — impact tells us more than the category name;
- a screenshot, short video or proof-of-concept, if it makes confirmation quicker;
- how you would like to be credited, if you want to be.
English is the language we can act on fastest.
5. What you can expect from us
- Acknowledgement within 3 business days that a human has your
report;
- An initial assessment — valid, duplicate, out of scope, or
needs more information — within 10 business days;
- Progress updates at reasonable intervals while we work on a fix;
- Confirmation when the issue is resolved, and credit on request.
We do not run a paid bug bounty and cannot offer a monetary reward.
6. Safe harbour
If you make a good-faith effort to follow this policy, we will treat your research as
authorized conduct. We will not pursue legal action against you over it, and if a third
party brings action over activity that stayed within this policy, we will make it known
that your testing was authorized by us.
This covers our own systems only. It does not extend to activity that breaks the rules
in section 3, that targets client or third-party systems, or that is unlawful on its own
terms, and nothing here waives any right of a third party.
7. Public disclosure
Please coordinate with us before publishing. Our default is that you may publish 90 days
after your initial report, or sooner once a fix has shipped and we have agreed a date. If
we need longer, we will explain why rather than go quiet.
8. Encrypted reporting
We do not publish a PGP key at this time, so our
security.txt carries no
Encryption field. If a report needs to be encrypted, send a
first message without the sensitive detail and we will arrange a channel.
9. Contact
Security reports and questions about this policy:
info@qcramai.com or the
contact form. This policy sits alongside our
Terms & Conditions,
Privacy Policy and
Disclaimer.