Security audit / outside-in and web applications
Security audit
Brightmoor Logistics SRL
brightmoor.example
Security Audit, by ACIDRIPP
See your company the way an attacker does: every server, site and leaked staff account you expose, which weaknesses are real, and what to fix first. Proven, in plain language.
Request an auditOnly systems you own or may have checked / written permission first
Security audit / outside-in and web applications
Security audit
Brightmoor Logistics SRL
brightmoor.example
What we check
If your company runs it, rents it or forgot it, it is in scope, as long as you are allowed to have it checked. Product names belong to their owners.
Why now
Finding a forgotten server, writing a convincing fake invoice or trying a newly published flaw used to take skill and time. AI made all three cheap. That is why we built our audit around the same speed.
01 / They find you
Automated tools look at every address for old servers, open doors and sites left online. They do not choose targets. They take whatever is exposed, and a company of ten looks the same to them as a bank.
02 / They move fast
When a weakness is published, AI helps attackers turn it into a working attack before most companies have read the news. We check yours against the flaws criminals use right now, first.
03 / They sound like you
AI writes in your tone, in Romanian or any language, without the mistakes that used to give scams away. If your domain lets anyone send mail in your name, your customers cannot tell the difference.
The law
More and more countries now require companies to keep their systems secure and up to date, and to prove it. The fines are real, and management answers for them personally.
To be plain about it: an audit does not make a company compliant on its own, and we never say it does. It gives you what the new duties expect you to have: a dated record of what you expose, proof of what is wrong, and a fix list you can show you acted on.
The EU's cybersecurity directive covers far more companies than before, including transport, logistics, manufacturing, food, waste, digital services and their suppliers. Directors must approve the security measures and are accountable when they are missing.
Romania's NIS2 law. Companies in scope have to register with DNSC, the national cybersecurity authority, which can inspect them and fine them.
Every company that keeps personal data has to secure it, and report a breach within 72 hours. Failing to secure it can cost up to €10m or 2% on its own; leaving customer data where anyone can download it is exactly what the fines are for.
Banks and their IT suppliers already work under DORA, makers of connected products face the Cyber Resilience Act, and more insurers and large customers now ask for proof of security before they sign.
What one forgotten hole costs
Almost every breach starts with something nobody was watching: an old test site, a leaked password, a device nobody updated. Here is what it turns into.
A sub-site you stopped using still points at a server someone else now controls. It shows spam, fake shops or worse under your domain name, with a valid padlock. We found eleven of these at a single company.
Search engines punish domains that serve spam or malware and browsers put warning pages in front of them. Climbing back can take months of work your marketing already paid for once.
A fake invoice from your address, with a new bank account, reaches the people who trust you most. They pay, and it is your reputation that takes the loss.
Customer records, invoices or contracts end up online. You have 72 hours to report it, customers to tell, and a fine to expect.
Ransomware locks every computer behind the one box that was not updated. Orders, invoices and email stop until it is rebuilt, if the backups survived.
What sets it apart
A scanner gives you thousands of alerts and leaves you to guess. We do the guessing for you, by hand, and only report what is real.
Each one carries its evidence and how sure we are. In one real audit, 27,347 automated alerts became 13 findings, and the most serious one was not in the automated output at all.
The first pages explain in plain words what is wrong and what it means for the business. The rest gives your IT people the exact detail and the fix order.
We check your people's addresses against 10.6 billion leaked records and tell you who is exposed. Passwords never appear in a report.
Nothing is tested before you sign what may be checked and when. Every step is planned, logged and stays inside that permission.
Every revision is signed and dated, so an auditor, insurer or customer can check it is genuine and was not changed afterwards.
01 / Map
Most companies expose far more than they think. We start from your domain name and find the rest.
We started from one thing, your domain name. Public certificate records and DNS led to 23 sub-sites and 6 servers. These are the ones that matter:
| Address | What it is | Result |
|---|---|---|
| www.brightmoor.example | Your website | fine |
| shop.brightmoor.example | Your web shop | fine |
| portal.brightmoor.example | Customer portal | Finding 5 |
| vpn.brightmoor.example | VPN gateway | Finding 2 |
| files.brightmoor.example | Invoice storage | Finding 3 |
| test.brightmoor.example | Old WordPress test site | Finding 8 |
| mail.brightmoor.example | Mail server | Finding 9 |
16 more sub-sites point nowhere or redirect to the main site. They are listed in the appendix so you can tidy them up.
02 / Check
We compare what you run with every known weakness, starting with the ones criminals use today.
The box that lets staff work from home runs a software version with a known flaw. It lets a stranger take over the box without a password.
The flaw is on the US government's list of weaknesses that criminals are exploiting right now (CISA KEV), and attackers use it to get into company networks.
The VPN box sits between the internet and your office network. Whoever controls it can reach every computer behind it.
We confirmed the version from what the box tells every visitor. We did not try the attack: that would put your office network at risk, and the version alone is enough.
vpn.brightmoor.example:443 SSL VPN login page
reported version 7.2.4
known flaw CVE-2024-21762, out-of-bounds write
on CISA KEV since 9 February 2024 actively exploited
fixed in 7.2.7 and later03 / Prove
Where it is safe, we demonstrate the problem, so nobody can argue it away. Where it is not, we say why we stopped.
When the website was last updated, the developer's working folder (called .git) was copied to the server with it. Anyone who knows where to look can download it, and with it the whole history of the site's code.
One of the files in that history holds the password the customer portal uses for its database.
With that password, someone on the internet can read every customer account in the portal: names, addresses, orders. That is a personal data breach you would have to report to ANSPDCP within 72 hours.
Tools that look for this run against millions of sites every day. It is one of the first things they try.
GET https://www.brightmoor.example/.git/HEAD 200 OK ref: refs/heads/main Downloaded 412 objects, rebuilt the code history config/database.php, commit 7f3a2c1 (March 2025): 'host' => 'portal-db.internal' 'password' => 'K*************2' (masked in this report)
04 / Expose
A leaked password is the cheapest way into a company. We tell you whose, so you can close it before someone uses it.
We checked all 51 addresses on your domain against 10.6 billion leaked records. 14 appear in at least one leak. For 6 of them a password leaked too, and 2 of those passwords still opened the account's webmail when the owner tried them in front of us.
| Account | Where it leaked | Password too |
|---|---|---|
| j****.p*****@brightmoor.example | 2023, file-sharing service | yes |
| o****@brightmoor.example | 2024, online shop | yes |
| a*******@brightmoor.example | 2021, social network | no |
Passwords are never printed in a report, never sent by email and never kept with your data. Addresses are masked here; your copy names them so you know whom to call.
05 / Fix
Not a hundred pages of warnings. A short, ordered list of fixes, with how long each one takes.
| # | What to do | Closes |
|---|---|---|
| 1 | Remove the .git folder from the web server and change the database password | Finding 1 |
| 2 | Update the VPN gateway to the vendor's fixed release, then check its logs since September | Finding 2 |
| 3 | Make the storage bucket private and turn on access logging | Finding 3 |
| 4 | Reset those 6 passwords and require two-step sign-in for every account | Finding 4 |
| 5 | Lock out after repeated failures and add two-step sign-in for staff | Finding 5 |
| 6 | Publish a DMARC policy, move it to reject after two weeks | Finding 6 |
| 7 | Close port 3389 on the warehouse router; use the VPN instead | Finding 7 |
| 8 | Delete test.brightmoor.example, or put a password in front of it | Finding 8 |
| 9 | Renew it, and turn on automatic renewal | Finding 9 |
06 / Keep watching
An audit is a picture of one day. With a subscription we check again every month, and tell you the moment something new affects you.
It was added to the list of actively exploited weaknesses this morning. Your shop runs the affected version 4.1.2. Update to 4.1.5 today; it takes five minutes in the WordPress dashboard.
A password leaked with it. Ask the person to change it, and anywhere they used the same one.
23 sub-sites checked, nothing new exposed. The certificate on mail.brightmoor.example renews automatically now.
Sample report
A complete sample, for an invented logistics company: the summary for decision makers, what the internet can see, the findings with their proof, leaked accounts and the action plan.
Your main website and your shop work well and we found nothing wrong with how they look to a visitor. The problems are in what sits around them: a website folder that gives away a password, a VPN that needs an update, and customer invoices anyone can download.
Two findings need action this week. Items 1 and 2 together remove the realistic risk of someone getting into your systems, and both are a morning's work for whoever looks after your servers.
| # | Severity | Finding |
|---|---|---|
| 1 | Critical | The company website hands out its own source code, with the customer portal's database password inside |
| 2 | Critical | The office VPN runs a version with a flaw criminals are using right now |
| 3 | High | 2,140 customer invoices can be listed and downloaded by anyone from cloud storage |
| 4 | High | 14 staff email accounts appear in public data leaks, 6 of them with a password |
| 5 | High | The customer portal accepts unlimited password guesses |
| 6 | Medium | Anyone can send email that claims to come from @brightmoor.example |
| 7 | Medium | Remote desktop on a warehouse PC is reachable from the internet |
| 8 | Low | A forgotten WordPress test site runs four plugins past their support |
| 9 | Info | The certificate on mail.brightmoor.example expires in 9 days |
Proven: we showed it works, without changing or keeping your data. Confirmed: checked by hand against your systems.
Behind every audit / counted 10 November 2026
Pricing
Every company is different, so we agree the scope with you first and send a fixed quote. These are the starting prices, before VAT.
Audit
from €1,000 one time
A one-off audit of what your company exposes: we map it, check it, prove what is real and tell you what to fix first.
Subscription
from €50 / month
We keep checking after the audit, so a new hole is found by us and not by an attacker.
Subscription
Price on request
For companies that have to show regulators, insurers or customers that their security is in order.
The audit price depends on how many sites, servers and apps you have; a small company with one website and email is at the starting price. Inside tests (office network, Windows domain, cloud accounts) are quoted separately.
Questions
Most attacks are automated and do not pick targets. They find whatever is exposed and use it. The audit shows you what they would find.
Checks from the outside do not touch the inside of your systems. Anything more intrusive is planned with you, approved in writing and run in a window you choose.
A scanner lists possibilities. We show which ones really affect you, with proof, and in what order to fix them. Bring your scan; we will tell you which of its alerts matter.
It stays on our own machines in the EU, every action is logged, and leaked passwords are never put in a report. When the work is done, we keep only the report and its evidence, for as long as you want us to.
It gives you the evidence and the fix list the new duties expect you to have. Compliance itself depends on your whole organisation, so we do not certify it, and nobody honest can after one audit.
For a small company, about a week from your signed permission to the report, and the walkthrough call right after. Fixes are usually a few hours of your IT person's time.
Request an audit
Tell us who you are and we will call you. Nothing is checked until you agree.
Only systems you own or may have checked / written permission first
Request received
We sent a link to . Open it to confirm the request; it works for 7 days. Once you confirm, we call you within two working days.