Updated November 7, 2026. Security controls listed here match the AIMS360 security overview.
What to include in a vulnerability report
A clear report gets a faster fix. The more of this list you can give us, the less back and forth there is before our team can reproduce the issue.
| Include | Why it helps |
|---|---|
| A short summary | One or two sentences on what the weakness is and what it lets someone do |
| Where it is | The URL, screen, API endpoint or app feature, and the AIMS360 company or test account you used |
| Steps to reproduce | Numbered steps from a fresh login, with the requests or inputs you sent |
| Proof | Screenshots, a short screen recording or request and response logs, with any personal data removed |
| Impact | What data or actions an attacker could reach, and under what conditions |
| How to reach you | An email address we can reply to, and whether you would like to be credited |
What happens after you report a vulnerability
AIMS360 runs as a cloud service, so most fixes reach every company at once, with no download or install on your side.
- We confirm we received it
Our team acknowledges the report and opens a case so it is tracked from start to finish.
- We reproduce and assess it
Engineers follow your steps, confirm the issue and judge how serious it is and which companies it could affect.
- We fix and test
A fix is built and tested away from live customer data, then released to the AIMS360 cloud.
- We tell the people affected
If customer data or settings were at risk, affected companies are told what happened and what, if anything, they need to do.
- We close the loop with you
You hear when the fix is live, and we agree together when and how details can be shared.
Ground rules for security testing
How AIMS360 protects your data day to day
Reports are one layer. The controls below are the rest, as published in the security overview and on the data security page.
| Area | What AIMS360 does |
|---|---|
| Hosting | Microsoft Azure, in East US (Virginia) and West US (California). Each company's database, files and backups stay in its region |
| Network | Azure Firewall filters traffic, and Azure Web Application Firewall blocks common web attacks such as SQL injection and cross-site scripting |
| Monitoring | Azure Monitor watches the environment and alerts on unusual activity |
| Encryption | At rest with Transparent Data Encryption in Azure SQL using AES-256, in transit with TLS, and at the column level for sensitive fields |
| Access | Role-based permissions, so each person sees what their role needs. Costing and margin can be restricted |
| Card data | Payments run through a PCI DSS compliant gateway. AIMS360 keeps a token and the transaction reference, never the full card number |
| Development | The team works on cleansed data or an isolated sandbox, not live customer records |
Reporting a vulnerability: FAQ
Email support@aims360.com with Security in the subject line. Include a summary, where the issue is, steps to reproduce, proof and the impact.
Yes. AIMS360 investigates every report, works with the reporter on a fix and a timeline, and asks that details stay private until the fix is live.
Only against your own company or a test account, without disrupting the service or touching other companies' data. Stop and report as soon as you see data that is not yours.
Yes. You hear when the fix is live, and we agree with you when and how details can be shared.
Usually not. AIMS360 is a cloud service, so a fix released to the AIMS360 cloud reaches every company. If an action is needed on your side, we tell you.
The AIMS360 security overview and the data security page cover hosting, encryption, access, backups and card data. For a full review, email hello@aims360.com.
This policy may change. The version on this page is the current one.
.png)









