Services
A security check of the running stack
The useful check starts with the doors that are already open: an admin path, a token in a repo, a dependency with a known hole.
We look at the system you run, not a generic questionnaire. Findings are ordered by what an outsider could try first.
When it fits
- The application is public and has not had an outside look.
- Repositories, old config files, and dependencies have not been reviewed in a while.
- You want a short, ordered list of fixes, not a long report.
How the work goes
- We review auth, sessions, file access, and the public routes.
- Dependencies are checked against known advisories.
- Repositories and old config files are searched for secrets.
- Each finding says where it is, how it could be used, and the smallest change that closes it. The list is ordered by what an outsider could try first.
Example: close what is open
Already open
The check starts with what is already reachable. Pick one.
What you receive
- Findings ordered by what to close first
- A note on what was checked and what was out of scope
- Fixes small enough to schedule in the current sprint
How to start
Send the address of the application, access to the repository, and anything that is out of scope. Email it to info@developerlab.nl, or see the contact page for other ways to reach Puya Sarmidani.
Send an email