Report a security issue
If you found a vulnerability in A-Line.cloud or this website, tell us here. A person reads every report, we answer within 3 working days, and we will not take legal action against research that follows these rules.
Last updated
You do not need an account to report. Fill in what you know. Only the title, where it is, how serious you think it is, a description and your email are required; we ask for the rest if we need it.
Send a report
The form is on the web page; email security@a-line.be instead.
Prefer your own mail app? Email security@a-line.be
Do not include customer data or secrets you found. If you have files, logs or a long proof of concept, say so in the form and we reply with a private way to send them.
Our approach
A-Line Services is run by one person, Arthur De Witte, who reads every report. We would much rather hear about a problem from you than from someone else, so we want reporting to be easy and safe.
This page says what you can test, what we ask of you, what you can expect from us, and how we handle credit and rewards. It follows the ideas of coordinated vulnerability disclosure (ISO/IEC 29147) and the Belgian rules for ethical hackers, described at the end.
What is in scope
These are ours, and we want reports about them:
- a-line.be, this website, and its form API under a-line.be/api
- The A-Line.cloud console at a-line.cloud and its sign-in at id.a-line.cloud
- The A-Line.cloud API at api.a-line.cloud and the MCP server at mcp.a-line.cloud
- The container registry at registry.a-line.cloud
- The platform itself: for example a way to reach another customer's apps, data, clusters or billing, to get permissions you were not given, or to break out of your own workload into the platform
- The other subdomains of a-line.cloud and a-line.be that we run, such as docs.a-line.cloud and the status page
Sites and apps that customers run on A-Line.cloud, including those on a-line.dev addresses, belong to those customers and are out of scope. If the flaw is in the platform that serves them, it is in scope, and we want to hear about it. If you are not sure whose it is, report it anyway.
Our other products and services (for example A-Line CMS and SquarePic) have their own websites. Report problems with those to the same address on this page and say which one; we will pass it on to the right place.
If an asset is not on this list, ask first through the form. We add what we run to this page.
What is out of scope
Please do not report these, they take time from real problems:
- Denial of service, load testing and anything that degrades the service for others
- Social engineering, phishing or other attacks on people, including A-Line staff and customers
- Physical attacks on offices, data centres or devices
- Spam and abuse of the contact or request access forms, unless you found a way past the bot check that lets you send mail we did not agree to
- Output from automated scanners that has no demonstrated impact
- Missing security headers, cookie flags, SPF or DMARC records and similar hardening advice with no impact you can show
- Reports that need a rooted or modified device, an outdated browser, or a victim who has already lost control of their account or machine
- Software versions or banners without a working exploit
- Findings in services we use but do not run, such as our hosting providers, GitHub, our email provider or the payment provider. Report those to the vendor.
- Vulnerabilities that only affect your own account or your own apps and cannot reach anyone else
Not sure whether something counts? Send it. We would rather read a borderline report than miss a real one.
Rules
Research is welcome when you:
- Test only with your own account and your own data, or with accounts that belong to people who agreed. Do not use or change other customers' data.
- Stop as soon as you have shown the problem. Look at the least data you need. If you see personal data, do not copy, keep or share it, and tell us what you saw.
- Do not disrupt the service: no denial of service, no heavy automated scanning, no spam, no tests that could delete or alter data you do not own.
- Do not use a flaw to get further than you need: no moving between systems, no persistence, no installing anything, no pivoting into customers' apps.
- Do not threaten us or ask for payment in return for not publishing or not reporting.
- Keep the details private until we have fixed the problem or agreed a date with you (see Timelines).
- Follow the law that applies to you. We can only speak for ourselves.
What you can expect from us
When you report in good faith and follow these rules, we promise to:
- Acknowledge your report within 3 working days, with a reference number.
- Tell you whether we can reproduce it, and how serious we think it is, within 10 working days.
- Keep you updated at least every 2 weeks until it is fixed, and tell you when it is.
- Treat your report and your details as confidential, and share them only as far as needed to fix the problem.
- Credit you by name or handle if you want, or keep you anonymous if you prefer.
- Not take legal action against you, and not report you to the authorities, for research that follows these rules. We consider such research authorised, and we will not hold it against the terms of this website or of A-Line.cloud.
That promise is ours. We cannot bind other people, such as our customers' own sites, our providers, or authorities in other countries.
Timelines
We are one person, so these are targets, not guarantees. We will tell you early if we are going to miss one.
- Acknowledgement: within 3 working days.
- First assessment (reproduced or not, and how serious): within 10 working days.
- Fix: we aim for 7 days for critical issues, 30 days for high, 90 days for medium, and the next regular release for low. Hard problems take longer, and we say so.
- Updates: at least every 2 weeks.
Disclosure: we ask you to keep the details private until the problem is fixed, or for 90 days after your report, whichever comes first, and to agree any earlier or later date with us. Once it is fixed we are glad to agree to a joint write-up or to you publishing your own. After 90 days we will not unreasonably refuse permission to publish. If a fix needs longer, we ask for more time and explain why.
Severity
When you report, you pick the level you think fits. We make the final call and tell you why if we differ.
- Critical. Someone can take over the platform or reach other customers' data or systems with little or no effort.
- High. Someone can read or change data or settings that belong to others, or take over an account, with some conditions.
- Medium. A real weakness with limited reach, or one that needs a lot of effort or an action by the victim.
- Low. A minor weakness with little practical impact.
You can also give a CVSS 4.0 or 3.1 vector if you know it. It helps, but it is not needed.
Rewards
We do not run a bug bounty with fixed prices. We are a small company, and we will not promise money we have not budgeted.
What we can promise is that a good report is always thanked, and credited if you like. For a report that shows a real, previously unknown problem with real impact, we may also offer a reward in euro, at our discretion. How much depends on how serious it is, how many people it could affect, and how clear your report is: steps we can follow, impact explained, and a suggestion for the fix help a lot.
Rewards are never a condition for reporting, and we never pay for silence. Reports of out-of-scope issues, of issues we already knew about, of problems found by breaking the rules above, and duplicate reports (the first one counts) do not qualify. If we offer a reward, we will agree the amount with you before paying it. We may ask for the details we need to pay you (for example an invoice).
With thanks
No one is listed yet, so the first spot is open. When your report leads to a fix, you can have your name or handle here, with the month, and a link if you like.
Credit is always your choice. Say in the form how you want to be named, or that you want to stay anonymous.
The law in Belgium
A-Line Services is a Belgian company. Belgian law (article 23 of the law of 26 April 2024 establishing a framework for the cybersecurity of networks and information systems, which brought in the NIS2 rules) protects ethical hackers from criminal prosecution when they meet certain conditions: they have no intent to defraud or harm, they do not go beyond what is necessary and proportionate, they notify the organisation and the Centre for Cybersecurity Belgium (CCB) promptly, and they do not disclose the vulnerability publicly.
Reporting to us through this page notifies us. The CCB's guidance treats a report made under an organisation's own disclosure policy as covering the notification, and the CCB is the national point to turn to if you prefer, or if we do not answer. Read the CCB's guidance before you start if you want to be sure of your position.
This is general information, not legal advice. It covers Belgian criminal law, not other countries' laws, and it does not bind anyone but us.
Changes
If this page changes in a way that matters to you, we change the date at the top and say what changed.
Questions about this policy, or a report that does not fit the form? Write to security@a-line.be.
Machine-readable version: security.txt