This guide is for CTOs, product owners and operations leads who run a live web or SaaS application and buy maintenance from one supplier and security testing from another. It shows what a combined service contains, how to split ownership if you keep two suppliers, and when combining them is the wrong choice. For the testing itself, see application security testing; for the day-to-day upkeep, see application maintenance and support.
In this guide
- Why do security and maintenance drift apart in a live application?
- What does "patched, scanned and recoverable" mean in practice?
- Who owns a finding from scanner to patched release?
- Three ways to buy it
- How to set up one service for a live application
- When should you not combine security and maintenance?
- Where AI fits
- What delivery record exists, and what does not?
- Alternatives: other routes and how to choose
- Limits of this guide
- Frequently asked questions
- Next step
Why do security and maintenance drift apart in a live application?
Security and maintenance drift apart because they are usually bought as two contracts with two owners. The tester delivers a report, the maintenance team works from a ticket queue, and a finding becomes nobody's next task. The application stays live, but its patches, scans and backups no longer follow one plan.
A yearly penetration test produces a list of findings; the maintenance retainer covers bug fixes and small changes, so security fixes compete with feature requests. A dependency scanner runs in the pipeline, but its warnings are not in anyone's service levels. Backups run every night, and nobody has restored one since launch.
Each of these gaps is a missing hand-off, not a technical failure. NIST describes patching as "a critical component of preventive maintenance for computing technologies" and a cost of doing business, which is the point: security upkeep is maintenance work, and it needs the same owner, schedule and budget line as any other maintenance.
Runtimes and frameworks also expire on a fixed timetable. PHP, for example, gives each release branch two years of active support and two further years of critical security fixes only, after which the branch is no longer supported. An application nobody upgrades will eventually run on software that receives no patches at all.
What does "patched, scanned and recoverable" mean in practice?
A live application is patched when known fixes for its runtime, framework and libraries are applied on a schedule, scanned when its code, dependencies and running endpoints are checked for new weaknesses, and recoverable when a restore from backup has been tested recently. Each of the three leaves evidence a buyer can ask to see.
-
Patch
- Cadence
- Per change and monthly
- Work done
- Library and framework updates, runtime upgrades planned before end of life
- Evidence it leaves
- Changelog entries, upgrade plan, version list per environment
-
Scan
- Cadence
- Per change and weekly
- Work done
- Dependency scan in the pipeline, scheduled scan of running endpoints, certificate and configuration checks
- Evidence it leaves
- Scan history, triaged findings with owners
-
Test
- Cadence
- Before major releases and at least yearly
- Work done
- Penetration test or focused security review of the riskiest flows
- Evidence it leaves
- Report, fix records, retest result
-
Recover
- Cadence
- Quarterly
- Work done
- Restore a backup to a separate environment and check data and login
- Evidence it leaves
- Restore log with date, duration and gaps found
The cadence is a starting point, not a standard; agree it per application, by how much data and money the application handles. For the certificate part of the weekly scan, the AdminKit SSL/TLS check from AdminKit, a Netbase brand, gives a quick certificate and cipher check for a website.
Who owns a finding from scanner to patched release?
One person should own each finding from the moment it is reported until the fixed version is released and verified. When security and maintenance are separate contracts, ownership changes hands at least twice, and the finding is most likely to stall at the second hand-off, between the triage decision and the release.
-
Report the finding
Scanner or tester, into the maintenance backlog
- Maintenance vendor plus tester
- Tester, into a PDF report
-
Decide severity for this business
Service owner with the client's product owner
- Maintenance vendor plus tester
- Client, often without the tester present
-
Fix at the root cause
The maintenance engineers who know the code
- Maintenance vendor plus tester
- Maintenance vendor, if the fix fits the retainer
-
Release and verify
Same team, through the normal release process
- Maintenance vendor plus tester
- Maintenance vendor releases; tester retests later
-
Close with evidence
Ticket links finding, commit, release and retest
- Maintenance vendor plus tester
- Spread across two systems
Severity scores help with ordering, but they are not the whole answer. FIRST's Exploit Prediction Scoring System estimates the probability that a published vulnerability will be exploited in the wild in the next 30 days; combined with what data a component touches, it helps decide which patch goes first.
Three ways to buy it
Compare the routes by who fixes, who verifies and who answers when something breaks.
| Option | Strength | Risk | Choose it when |
|---|---|---|---|
| One combined service | One owner per finding, one cadence, one release process | Less independence: the team checks its own work | You want fewer hand-offs and can add an independent test once a year |
| Maintenance vendor plus independent tester | Independent findings, clear audit evidence | Findings stall between report and fix; retest timing drifts | An auditor or customer requires independent testing as evidence |
| In-house team with tools | Full control, knowledge stays inside | Scans and restores slip when feature work is busy | You have engineers with time reserved for upkeep every sprint |
A combined service does not remove the need for independent testing; it changes its role. The independent test becomes a periodic check on a service that already patches and scans, not the only security activity of the year.
How to set up one service for a live application
-
Inventory what is running
List environments, runtimes, frameworks, libraries, third-party services and where data and backups live; note every component already at or near end of life.
-
Write one backlog
Put security findings, patches and feature requests in the same queue, with a severity rule that says which security items jump ahead of features.
-
Automate the scans
Run dependency checks on every change and a scheduled scan of the running application, and route results to the backlog, not to an inbox.
-
Set the patch rhythm
Agree a monthly patch window for routine updates and an emergency path for actively exploited vulnerabilities, both through the normal release process with tests.
-
Plan upgrades before end of life
Put each runtime and framework end-of-life date on the roadmap a quarter ahead, so an upgrade is a planned release, not an emergency.
-
Rehearse recovery
Restore a backup to a separate environment each quarter, log what failed, and fix the gaps before the next rehearsal.
-
Book the independent check
Schedule a yearly penetration test with its retest against a stable release, and feed the findings into the same backlog.
-
Report monthly
Share the patch level, open findings by age and severity, and the last restore result in one short report the product owner can read.
When should you not combine security and maintenance?
Do not combine them when you need independent testing as audit or customer evidence and have no budget for a separate yearly test, when the application will be retired within months, or when the maintenance team cannot fix code it did not write yet. In those cases separate contracts, or a short takeover first, fit better.
A customer security questionnaire may accept your own scan history, while an audit may expect an outside tester. A combined service should say clearly which of its outputs are self-checks.
A team that has just taken over an application needs time to learn the code before it can own security fixes safely. Start with the inventory and the scans, and move ownership of fixes over once the team has shipped a few releases.
Where AI fits
AI helps with the volume of upkeep. A model can summarise changelogs for a library update, group duplicate scanner findings, draft the upgrade checklist for a framework version, and draft regression tests for a patched weakness. Engineers still decide severity, review every generated change and confirm that a restore really worked, because a confident summary of a breaking change is worse than none. Netbase works with the major commercial and open-source AI tools and models, chosen per project.
- Available capability
AI-assisted upkeep under human review
AI-assisted changes pass the same secure code review, version control and scanning as any other change; not yet tied to a published maintenance case.
What delivery record exists, and what does not?
Netbase's published security practices are secure code review and version control, TLS in transit and AES at rest, role-based access control, MFA for admin dashboards, vulnerability scanning and penetration testing, and disaster recovery; NDAs, data processing agreements and SLAs are available on request.
Netbase runs, maintains and upgrades what it builds, remotely and alongside the client's in-house team, under an agreed support scope, and response targets are set per contract. Printcart, a web-to-print and print-on-demand platform and one of the Netbase Business Divisions, is an application Netbase builds and keeps running.
For an existing client store Netbase had built, Netbase scoped the recovery of a compromised Magento site in three phases: investigation and a malware scan of code, database and server; cleanup with core files restored; then repair, Magento security patches and hardening. The client is not named, and recovery is scoped after the scan, never guaranteed before it.
Netbase holds ISO 27001 certification and a SOC 2 Type II attestation for its own operations; they do not cover a client's application. Most Netbase projects are delivered on fixed-price contracts; milestone-based, monthly retainer and KPI-linked models are also offered. No uptime figure, incident count, patch time or response time is published.
Alternatives: other routes and how to choose
- Managed hosting with security add-ons. Covers the server, operating system and backups, but not your application code or its libraries; pair it with managed cloud services only if someone else owns the code.
- Security checks inside the pipeline only. The secure development lifecycle catches new weaknesses before release, but it does not patch what is already live or rehearse recovery.
- Release-time testing only. Quality engineering and testing protects each release, not the months between releases.
- Mobile apps. Store releases and OS support windows change the rhythm; see mobile app maintenance, security and release operations.
Choose by three criteria: who can ship a fix fastest without breaking the release, who can show evidence of each loop on request, and who still answers for the application when the original developers have left.
Limits of this guide
- It covers custom web and SaaS applications, not office IT, networks or endpoint security.
- The cadences are starting points to agree per application, not a compliance standard or legal advice.
Plan the next step with a Netbase consultant
Frequently asked questions
Yes, if the same team patches the application, owns scan findings until they are released and rehearses recovery. Keep one independent test a year when customers or auditors need outside evidence, because a combined team checks its own work.
Apply routine library and framework updates in a regular monthly window and actively exploited vulnerabilities as an emergency release. Plan runtime and framework upgrades before their end-of-life date, so the application never runs on software without security fixes.
No. A penetration test checks one release at one moment. Between tests, dependency scans, scheduled scans of the running application and a monthly patch rhythm find and close new weaknesses as they are published.
Restore a recent backup to a separate environment, check that data and logins work, and record how long it took and what failed. A backup that has never been restored is an assumption, not a recovery plan.
Next step
If your live application is maintained by one supplier and tested by another, and you want one plan for patching, scanning and recovery, book a solution review.
Related services and solutions
Application security assurance for web, SaaS and AI features Netbase provides application security testing for product and engineering leaders to find and fix vulnerabilities before release, including in AI features. We review code with AI-assisted triage, scan dependencies and test running applications, then rank findings and retest fixes. Netbase's own alignment with ISO 27001 and SOC 2 Type II covers Netbase's operations, never your application.
Learn More
AI-assisted QA and software testing that run inside delivery Netbase provides software testing and QA services for product and commerce teams to release often without breaking what customers use. QA runs inside delivery, not after it: acceptance criteria, automated regression with AI-generated test drafts, performance budgets and release readiness checks. Page speed shows the result: USticker's page load fell 21%, and PrintLeo's improved 35%.
Learn More
Application maintenance and support for live web, mobile and business software Netbase maintains and supports software that is already live: web platforms, online stores, mobile apps, ERP and CRM systems and internal tools, including software another vendor built. We take it over after a code and environment review, then fix defects, keep frameworks current, monitor it, make small changes and report monthly, under service levels agreed in your contract.
Learn More
SaaS product accelerator: launch an AI-ready SaaS on proven Netbase modules A SaaS product accelerator is a set of reusable Netbase modules for accounts, billing, roles and integrations that helps founders and product teams launch subscription software faster, with room for in-product AI from the first release. Reusing these modules can shorten development time, and the approach is proven on Printcart, Netbase's own web-to-print SaaS.
Learn More
Work with Netbase remotely
Every Netbase engagement is delivered remotely, so clients in any country and any industry can work with us; Netbase has worked with clients in 80 countries. Contracts and invoices are issued by Netbase JSC, and payment is made by bank transfer to Netbase JSC's company account or PayPal Business. Talk to the CEO, Huy Nguyen (David), on WhatsApp or by email.
Discuss a project
Netbase JSC helps organizations design, build, modernize, and operate digital products and AI-enabled business systems.project@netbasejsc.com
+84 937 869 689
91 Nguyen Chi Thanh, Dong Da, Hanoi, Vietnam
Get in touch
Tell us what you want to build, modernize, or operate.