Application remediation
Scope changes around identified application findings, affected user journeys, dependencies, and acceptance criteria.
Explore the capabilityApplication security & remediation
Application security engineering and remediation.
Engineering support for application security improvements within a defined software or modernization engagement. Salt can discuss implementation and verification work with your technical and security stakeholders.
What this offering covers
This page describes application engineering and remediation support. Availability and specialist requirements are confirmed after reviewing your scope. It does not advertise a managed SOC, emergency incident response, independent penetration testing, or compliance certification.
Where we can help
Choose the work
that matters now.
These are starting scopes. Your systems, decision owners, and delivery constraints shape the final proposal.
Access and workflow controls
Review how proposed roles, permissions, privileged actions, and record ownership should behave in your application.
Explore the capabilityDeployment and configuration work
Discuss approved configuration, dependency, secrets-handling, or environment changes as part of a scoped modernization workstream.
Explore the capabilityVerification and regression testing
Agree tests for affected behavior and critical journeys. Independent security assessment remains a separately defined responsibility.
Explore the capabilityDevSecOps delivery controls
Integrate agreed dependency, code, secrets, and container checks; define release gates, exception owners, and verification of fixes.
Explore the capabilityFrom discussion to delivery
A first engagement
with clear decisions.
- 01
Establish the boundary
Bring the application context, existing findings, permitted environments, and security decision-maker. Agree what can be inspected or changed and who approves access.
- 02
Prioritize the engineering work
Translate accepted findings into tasks with owners, dependencies, and verification criteria. Plan changes in a suitable test environment before a production release.
- 03
Verify and hand over
Record the changes, agreed test results, open issues, and operational responsibilities. Where specialist re-testing is required, coordinate the handoff to the designated assessor.
Delivery ownership
Choose how we work together.
A scoped remediation project
Suitable when findings and acceptance criteria can be defined. Confirm the required skills and scope before committing to delivery.
Discuss the right setupSecurity work within modernization
Suitable when application or infrastructure changes need to be coordinated with existing development and release responsibilities.
Discuss the right setupWorking with your US team
Agree time-zone overlap, communication channels, decision-makers, repository access, and review cadence before delivery begins. Scope, staffing, commercial terms, ownership, and post-launch responsibilities belong in the proposal and agreement.
Before you begin
Questions to resolve
before committing.
This offering does not include a verified 24/7 SOC, continuous threat monitoring, or incident-response retainer. Those services require a separately validated provider and scope.
Not by default. Independent penetration testing, certification, and formal compliance assessments must be explicitly scoped with qualified specialists. We can discuss engineering work arising from their findings.
No engineering engagement can guarantee the absence of vulnerabilities. Define the intended controls, verification evidence, remaining risks, and ongoing ownership for the particular system.
Start with a high-level description of the application, the category of issues, and the desired outcome. Do not send passwords, live credentials, or sensitive reports through the enquiry form; agree an appropriate sharing method first.
DevSecOps embeds security checks and ownership into development and release workflows. Application remediation implements changes for identified risks. These can be delivered together, with independent assessment or managed security operations scoped separately.
Start with a short brief
Discuss your security requirements.
Describe the affected application and the type of security work needed. Keep credentials, vulnerability details, and sensitive reports out of the initial enquiry.