Sample reportSample Security Assessment Report

Last updated 17 November 20267 min readSigosoft Private Limited

Web Application, API and Mobile App Security Assessment (VAPT)

Prepared by Sigosoft Private Limited for Northwind Retail Pvt Ltd (a fictional client), covering the Northwind customer web portal, its REST API and the Android app.

ItemDetail
Engagement IDSGS-VAPT-2026-041
Testing window3 to 14 November 2026
Retest26 November 2026
Report version1.1 (after retest)
ClassificationConfidential: client and Sigosoft only
Prepared bySigosoft security team, Kozhikode, India

This is a sample report. The client, systems, people and findings are fictional and were created to show the structure and depth of a Sigosoft security report. Real reports are shared only under NDA.

Document control

VersionDateChangeAuthor
1.127 Nov 2026Retest results added; 4 findings closedSigosoft security team
1.015 Nov 2026First issue after testingSigosoft security team

Distribution: Northwind CTO, Northwind Head of Engineering, Sigosoft engagement manager. Do not forward outside these recipients without written approval from both parties.

Executive summary

Overall risk was High before fixes and is Medium after the retest. We found 8 verified issues: 1 critical, 3 high, 2 medium and 2 low. The critical and two of the high issues are now fixed and confirmed by retest.

The most serious issue let any logged-in customer read other customers' orders, including names, phone numbers and delivery addresses, by changing an order number in the API. This was a personal data exposure that would have to be reported under India's DPDP Act once its breach rules apply. It was fixed within 48 hours and the fix was confirmed.

SeverityFoundFixed and retestedStill open
Critical110
High321 (fix in next app release)
Medium211
Low202 (scheduled)
Total844

What Northwind should do next

  1. Ship Android app version 3.8 with secure token storage before 15 December 2026 (finding F4).

  2. Trim the customer profile API response to the fields the app uses (F6).

  3. Add the missing security headers and generic error pages in the next web release (F7, F8).

  4. Re-test before each major release, and run a full assessment again in six months.

Scope and method

Testing was grey-box: Northwind gave us two customer accounts and one admin account on a staging copy that mirrored production. Nothing was tested on live customer data.

TargetIn scopeOut of scope
Customer web portalportal.northwind.example, all logged-in and public pagesMarketing site, third-party payment page
REST APIapi.northwind.example/v2, 46 endpointsPayment gateway callbacks
Android appVersion 3.7.2 (build 372)iOS app (next phase)
Admin paneladmin.northwind.exampleInternal network, staff laptops

Standards followed: OWASP Web Security Testing Guide, OWASP API Security Top 10 (2023), OWASP MASVS and MASTG for the Android app. Each finding is rated with CVSS 4.0 and then adjusted for business impact.

How we tested: automated scanning to cover breadth, then manual testing of logins, access control, business logic and data handling. Every finding in this report was reproduced by hand; scanner results that could not be confirmed were dropped.

Team: two in-house penetration testers holding OSCP and CEH, reviewed by an ISO 27001 Lead Auditor. Testing ran from Sigosoft's office IP ranges, which were shared with Northwind in advance.

Main tools: Burp Suite Professional, OWASP ZAP, Postman, MobSF, Frida, jadx, nmap and custom scripts.

Findings at a glance

IDFindingAreaSeverityCVSS 4.0Status after retest
F1Any customer can read other customers' orders (broken object-level authorisation)APICritical8.7Fixed
F2Password reset links never expire and can be reusedWebHigh7.7Fixed
F3Admin login has no MFA and no limit on password guessesAdminHigh7.6Fixed
F4App stores the login token in plain text and allows device backupAndroidHigh7.1Open, fix in v3.8
F5Stored cross-site scripting in product reviewsWebMedium5.3Fixed
F6Profile API returns more data than the app needsAPIMedium5.1Open
F7Missing Content-Security-Policy and other security headersWebLow2.3Open, scheduled
F8Error pages reveal framework and versionWeb, APILow2.1Open, scheduled

Detailed findings

F1. Any customer can read other customers' orders

Severity: Critical · CVSS 4.0: 8.7 · OWASP API1:2023 Broken Object Level Authorization · Status: Fixed (retested 26 Nov 2026)

What we found: the order details endpoint checks that the user is logged in, but not that the order belongs to them. Order IDs are sequential, so they are easy to guess.

Evidence: logged in as test customer A, we requested an order placed by test customer B and received it in full.

GET /api/v2/orders/100482 HTTP/1.1
Host: api.northwind.example
Authorization: Bearer <token of customer A>

HTTP/1.1 200 OK
{"orderId":100482,"customer":"<customer B name>","phone":"+91 9XXXX XXXXX","address":"<customer B address>", ...}

Business impact: anyone with a free account could collect the names, phone numbers and addresses of every customer who has placed an order. This is a reportable personal data breach and a serious reputational risk.

Fix: check on the server that the order's customer ID matches the logged-in user before returning it, and apply the same check to the invoice and returns endpoints. Optionally replace sequential IDs with random ones.

Retest: customer A now receives 404 Not Found for customer B's orders, invoices and returns. Closed.

Severity: High · CVSS 4.0: 7.7 · Status: Fixed

What we found: a reset link still worked 9 days after it was issued and could be used more than once. Anyone who later gets the email, for example from a shared inbox or forwarded mail, can take over the account.

Fix: make reset tokens single-use and expire them after 30 minutes; sign the user out of other sessions after a reset.

Retest: used and expired tokens are rejected. Closed.

F3. Admin login has no MFA and no limit on password guesses

Severity: High · CVSS 4.0: 7.6 · Status: Fixed

What we found: the admin panel is reachable from the internet, accepts unlimited login attempts, and has no second factor. We sent 500 guesses in 4 minutes with no lockout or alert.

Fix: require MFA for all admin users, lock or slow down after 5 failed attempts, alert on repeated failures, and restrict the admin panel to office and VPN IP ranges.

Retest: MFA is enforced, the sixth failed attempt is blocked for 15 minutes, and access from outside the allowed IP ranges is refused. Closed.

F4. App stores the login token in plain text and allows device backup

Severity: High · CVSS 4.0: 7.1 · OWASP MASVS-STORAGE · Status: Open, fix planned for app v3.8

What we found: the Android app saves the long-lived login token in SharedPreferences without encryption, and android:allowBackup="true" lets it be copied off the phone in a device backup.

Fix: store the token with Android Keystore through EncryptedSharedPreferences, set allowBackup to false (or exclude the token file), and shorten token lifetime with refresh tokens.

Retest: the fix is in the v3.8 build under review; it will be retested before release.

F5. Stored cross-site scripting in product reviews

Severity: Medium · CVSS 4.0: 5.3 · Status: Fixed

What we found: script code in a product review was saved and ran in the browser of anyone who opened that product page.

Fix: encode review text on output, sanitise HTML on input, and add a Content-Security-Policy (see F7).

Retest: the payload is shown as plain text and does not run. Closed.

F6. Profile API returns more data than the app needs

Severity: Medium · CVSS 4.0: 5.1 · OWASP API3:2023 · Status: Open

GET /api/v2/me returns 31 fields, including internal risk flags and staff notes, while the app uses 9. Return only the fields the app displays.

F7. Missing security headers

Severity: Low · CVSS 4.0: 2.3 · Status: Open, scheduled

The portal has no Content-Security-Policy, X-Frame-Options or Permissions-Policy headers. Add them in the web server configuration.

F8. Error pages reveal framework and version

Severity: Low · CVSS 4.0: 2.1 · Status: Open, scheduled

Unhandled errors show a stack trace with the framework name and version. Show a generic error page and log the details server-side.

Remediation plan

The four open findings have owners and dates agreed with Northwind. Sigosoft will retest each one when it is fixed, at no extra cost within 60 days of this report.

IDActionOwnerTarget dateRetest
F4Encrypted token storage and backup exclusion in app v3.8Northwind mobile team15 Dec 2026Before Play Store release
F6Limit /me response to the 9 fields in useNorthwind API team20 Dec 2026Within 5 working days of fix
F7Add CSP, X-Frame-Options and Permissions-Policy headersSigosoft (under support plan)10 Dec 2026Same day
F8Generic error pages; stack traces to server logs onlyNorthwind API team20 Dec 2026Within 5 working days of fix

Appendix: severity ratings

SeverityCVSS 4.0What it meansFix within
Critical9.0 to 10.0, or lower with severe business impactDirect exposure of customer data or full system takeover48 hours
High7.0 to 8.9Account takeover or serious data exposure with some conditions7 days
Medium4.0 to 6.9Harm needs extra steps or user action30 days
Low0.1 to 3.9Hardening gap that helps an attackerNext planned release

F1 is scored 8.7 by CVSS but rated Critical because of the volume of personal data exposed.

About this report

Sigosoft Private Limited is certified to ISO/IEC 27001:2022 (certificate 3050251230107IS, issued by QRO). Every finding is verified by hand, every fix is retested, and the report is suitable as evidence for ISO 27001, SOC 2 and client security reviews.

Contact: [email protected] · +91 98462 37384 · Sigosoft cyber security services

Questions about this policy?

Write to us at [email protected] and we'll respond within 2 business hours.

WhatsApp