Automated assessments
Every week, we assess the systems and environments defined in the scope. A specialist reviews the results, and you receive evidence, priorities and guidance to fix the issues.
Talk to a specialistFrom diagnosis to fix, side by side with your team.
Scope and preparation
We learn about your product, your business and your objectives to define a tailored scope. We align on assets, access, timelines and limits. Your team authorizes the scope and prepares the necessary access.
Investigation and review
Our specialists use proprietary technology to speed up the investigation and deepen the analysis. They verify the evidence and assess the impact of each finding in the context of your product and your business.
Delivery and priorities
We present the results and prioritize fixes by business impact. Management receives the priorities, and the technical team receives evidence and guidance to fix the flaws with the support of proprietary technology.
Fixes and retests
Your team implements the fixes. We verify the findings in the retest and record progress as set out in the contract.
Clarity to decide. Evidence to fix.
You receive evidence validated by specialists and fix priorities tied to the impact on your business, with depth and format defined for your program or project.
Learn about our methodologyThree priorities for this round
The risks below affect customer data and contract negotiations. The first item should be fixed before the next release.
- Data export without access controlRisk of customer data exposureHigh
- Sessions remain valid after a password changeRisk of account takeoverMedium
- Broad permissions on a service accountIncreases the impact of any unauthorized accessMedium
Data export accessible across organizations
An authenticated user can export records from another organization by changing the identifier in the request.
GET /api/v2/orgs/4817/export HTTP/2 Authorization: Bearer <token from organization 2093> HTTP/2 200 records from another organization
Recommendation: validate on the server that the user belongs to the requested organization before generating the export.
What was assessed and under what conditions
- Web application and authenticationTested with two access profilesAssessed
- Public API v2Staging environmentAssessed
- Payment webhooksNo partner credentials during the test windowInconclusive
- Android appOut of scope for this roundNot included
What changed since the last round
- Cross-organization data exportRequest now returns 403Fixed
- Sessions after a password changeMobile sessions still remain activeNeeds attention
- Service account permissionsPermissions reduced to what is neededFixed
Ready for your team or AI tool
Context: the GET /api/v2/orgs/:id/export route does not check whether the user belongs to the requested organization. Task: add the check on the server, before generating the export, and return 403 when the user is not a member. How to validate: repeat the request with a token from another organization and confirm the 403. Then confirm that legitimate members can still export normally.
Your team reviews and applies the change. The retest confirms the result under the contracted conditions.
Illustrative content. Depth and format are defined for your program or project.
Services
Shall we build your company’s security team?
In the call, we learn about your product, your risks and what your customers require. Then we show you where to start and send a proposal with scope, timeline and investment.
Talk to a specialist