Client: PaySecure · Security & Compliance · US retail payments (120 staff)

Removing Embedded Secrets from Payment Software

By TechSupport Team. Published November 16, 2026. Updated .

TechSupport Team maintained PaySecure’s Java and AWS payments application ahead of a PCI review. Over six months, client SonarQube records show hard-coded secrets falling from 14 to zero. Snyk recorded critical CVEs falling from 28 to 2.

Client and engagement facts

Client
PaySecure
Industry
Security & Compliance
Business context
US retail payments (120 staff)
Delivery model
Security maintenance
Application
Retail payments platform under PCI DSS
Supplied geography
US
Company size in source
120 staff

Application stack and tools

Application stack

  • Java
  • PostgreSQL
  • AWS
  • Vault

Tools used

  • Vault
  • Jira
  • Snyk
  • SonarQube

Why Support Was Needed

The team prioritized moving secrets into Vault and remediating critical dependencies. Two findings depended on changes from a payment terminal vendor.

Technical Work

  • Moved 14 hard-coded secrets to Vault.
  • Remediated dependency findings in severity order.
  • Recorded compensating controls for the two vendor-dependent items.

Representative Incident

The vendor patch was unavailable during the case window. The team documented two supplier-owned findings with compensating controls and recorded their accepted-risk status in the evidence trail.

Results and how they were measured

Reported results and their measurement scope
MetricBaselineResultUnitsMeasurement windowSource and scope
Critical CVEs2826 monthsClient Snyk
Secrets-in-code1406 monthsClient SonarQube

Evidence and Limitations

Two vendor-dependent items were documented with compensating controls and accepted-risk status. Critical-CVE and embedded-secret results are separate from those supplier-owned findings.

Supplier Findings in the Audit Trail

The team documented the vendor dependency, compensating controls and accepted-risk status in the audit trail.

Scope a Similar Engagement

Share the application’s dependency and secrets backlog, the relevant vendor boundaries and how findings are tracked. Request a support plan or explore software maintenance.

Get a technical support plan

Tell us which application needs support, what is reaching your engineers and when you need coverage. TechSupport Team will review the fit and explain the next scoping step.

  • We reply by email.
  • We agree a call about the roles, your stack and the hours.
  • If there is a fit, we propose engineers after an assessment.

A short outline is enough. Add your stack and coverage hours if you know them. Do not include credentials or customer data.

Add coverage and team details

We use these details only to reply to you. Describe the application, stack and hours you need covered. Keep credentials and sensitive technical data out of this form. We save the brief for delivery and use Telegram to notify our team.