Changelog

A weekly roundup of what's new in Trace.

Fix and verify findings faster and test apps behind Google sign-in

Fixing and retesting

  • Batch remediation. Select several findings on a pentest's page and mark them remediated at once.
  • Faster retests. Marking the last open finding in a pentest remediated starts its retest within seconds instead of ten minutes.
  • Clearer attestation letters. Letters now state when no Critical or High findings remain open.

Tracking findings

  • Org-wide finding numbers. Each vulnerability Trace reports now has one number that's unique across all pentests, such as PF-45. The numbers show up in search, reports, and the CLI.
  • Where to fix issues. Each finding names the application where the fix belongs. Other applications it affects are listed separately.
  • Easier-to-read repro scripts. The Reproduce tab shows what Trace ran and what each run returned.
  • Severity changes on disputes. A severity change from a dispute now shows in the finding's history.

Setting up a test

  • Apps behind Google sign-in. Trace can now test apps where people sign in with Google, with no shared password.
  • Credential notes. Tell Trace's testers what each test account is for and what to focus on.
  • Encrypted IPA warning. Trace now flags App Store and TestFlight builds it can't run as soon as they're uploaded.
  • AWS access update. For connected AWS accounts, an updated role lets pentests read more network configuration. Permission groups that were turned off stay off after the update.

Scan results

  • Clearer scan failures. Failed scans now explain what to do next in a short sentence instead of a raw error.

Onboarding and pricing

  • Code size estimate. tracecli code-size estimate measures billable lines of code locally. Use it to see which pricing tier fits.
TraceTrace
Get monthly product updates