Field Guide
$29
Choose the Field Guide when the test is close and you need the Fast Path, worked example, readiness checklist, evidence packet, and result template in one short operational guide.
Buy the Field GuideComplete Edition and Field Guide
Run a controlled mobile-security preflight before the pentest. Test ten failure areas across iOS, Android, and APIs, fix and retest avoidable findings, and retain credible evidence.
For the mobile lead or engineering manager who owns a release candidate and has a penetration test, enterprise security review, customer commitment, assurance audit, or regulated-product milestone approaching.
Choose an edition
$29
Choose the Field Guide when the test is close and you need the Fast Path, worked example, readiness checklist, evidence packet, and result template in one short operational guide.
Buy the Field Guide
$149
Choose Before the Pentest: Complete Edition when you need the full ten-check procedure, remediation and retest guidance, regulatory evidence mapping, and reference material. Your purchase also includes the Field Guide as a separate day-of reference.
Buy the Complete EditionContents preview
Three parts: set up the test, run the ten checks, and close the loop.
From the worked example
The fictional product is a business finance app. Two synthetic staff users belong to the same test company. Each created one reimbursement record.
The relationship matters. If user A were a company administrator, the same response might be expected behavior. The packet [the build, API deployment, test users, records, and expected rule] makes the authorization rule testable before the first request is replayed.
User A opened record A through the app. The tester captured the request, replaced A's record identifier with B's, and replayed it with A's unchanged session. The API returned B's amount, note, and attachment URL with
200 OK.Before the Pentest, “Worked Example: From Finding to Retest”Finding
The API returned 200 with B's amount, note, and attachment URL.
Retest
Observed result: 404 with no record fields; no attachment job or audit action created. Valid-flow result: A read record A successfully. Final status: Internally retested, ready for provider retest.
For the release team
$449
Give up to 10 internal readers at one company the Complete Edition and Field Guide. Suitable for mobile, API, QA, engineering-management, and security partners preparing the same release. Includes current-edition updates and internal-use rights, with no client redistribution or resale.
FAQ
The Field Guide is provided as PDF and EPUB. The Complete Edition includes the Complete Edition PDF and EPUB plus the Field Guide PDF and EPUB. The team license includes the same Complete Edition and Field Guide files plus the team license.
Refunds are allowed for 14 calendar days after purchase, or for the selling platform's longer mandatory refund window when one applies. The platform's delivery and refund records determine eligibility. This policy does not limit rights that apply under local law.
Purchasers receive corrections and minor updates to the edition they bought at no additional charge while the selling platform supports update delivery. A substantially revised future edition may be sold separately.
The license allows internal use by up to 10 readers in one legal entity. It does not allow public posting, resale, client distribution, sublicensing, or repackaging the books or templates as a separately sold course or service. Larger groups should request a separate license through Apps Done Wright.
This is engineering guidance for authorized testing. It does not replace a penetration test or establish compliance. It does not certify an application as secure and does not establish HIPAA, FDA, SOC 2, or other legal, regulatory, contractual, or audit compliance.
Pre-Pentest Readiness Help
If your pentest is already on the calendar and the release is still moving, I offer focused pre-pentest readiness work through Apps Done Wright. I can work with the engineers who own the mobile apps and APIs to assemble the test packet, run the highest-risk checks, record open findings, and prepare the handoff to the tester.