Dev48
Language
  • About
  • Services
  • Industries
  • Technologies
  • Articles
  • Contacts
Book a call
    Home/Articles/Beyond backups building cyber resiliency by design
Dev48
info@dev48.org+375 29 320-40-96WhatsApp@isky_by

© 2026 · All rights reserved.

Beyond backups: Building cyber resiliency by design

Source: HCLTech•November 17, 2026 at 03:06 PM

Beyond backups: Building cyber resiliency by design

Beyond backups: Building cyber resiliency by design Content Group Article pallavi.parashar Tue, 11/17/2026 - 10:28 Trends Channel Cybersecurity A business can recover every backed-up file and still be unable to serve a customer. Its identity platform may remain compromised, its applications may…

A business can recover every backed-up file and still be unable to serve a customer. Its identity platform may remain compromised, its applications may depend on an unavailable supplier or its restored databases may disagree about which transactions were completed. Cyber resiliency begins with understanding these conditions and deciding how the business will operate through them.

This requires a broader design brief for enterprise technology. Protecting information remains essential, but leaders must also ensure that critical business services can continue operating or be restored under hostile conditions. Architecture, operating procedures and investment decisions should therefore reflect what happens when prevention fails and parts of the environment become untrustworthy.

NIST’s Developing Cyber-Resilient Systems describes cyber resiliency through the capabilities to anticipate, withstand, recover from and adapt to adverse conditions and compromise. Its systems engineering perspective provides a useful foundation for treating resiliency as a lifecycle responsibility. The leadership implication is that resilience requirements belong in business planning and architecture reviews, before recovery becomes an emergency.

Why the backup mindset persists

Backup provides visible evidence of action. Jobs complete, copies accumulate and dashboards report success. Ownership is relatively clear, which makes data protection easier to procure and measure than the resilience of an entire business service. Enterprise accountability often follows the same boundaries: infrastructure owns availability, security owns threats and application teams own functionality.

Those boundaries become problematic during an attack. A service depends on connections across all of them. Restoring a server has limited value if users cannot authenticate or if a transaction requires a compromised integration. Successful backup metrics can coexist with a recovery process that nobody has tested from the customer’s perspective.

The commercial consequence is misplaced confidence. Executives may assume that additional copies reduce disruption proportionately, even when the binding constraint is an identity dependency or a manual recovery decision. Investment should follow the factors that determine business continuity, including people, access and suppliers, rather than the volume of protected data alone.

Organize around critical business services

Start with the activities whose interruption would cause unacceptable harm. Depending on the organization, these might include dispensing medicines, settling trades, scheduling production or accepting customer orders. Define the minimum acceptable service, the maximum tolerable disruption and the consequences of losing recent transactions.

A named business service owner should bring infrastructure, security, application and recovery leaders into a shared planning process. Each contributes specialist evidence. Security teams assess compromise scenarios, infrastructure teams identify operational constraints, application teams explain transaction behavior and recovery teams demonstrate what can be reconstructed. The service owner resolves priorities using business impact.

Consider a hypothetical distributor that can accept orders during an outage but cannot verify inventory. Its minimum service might permit order capture while withholding delivery commitments. That choice determines which systems must survive, which dependencies can be suspended and how staff communicate with customers. It also avoids restoring every component before useful operations resume.

Architecture across unequal environments

Hybrid estates need consistent service outcomes despite different technical controls. A legacy application may require a sequenced rebuild and specialist support. A cloud service may depend on permissions, deployment templates and encryption keys. A SaaS application may require recovery of tenant configurations, integrations and customer data through provider-supported mechanisms.

Resiliency by design makes these differences explicit. Architecture reviews should ask how each component is isolated, administered and reconstructed if its normal control environment cannot be trusted. Recovery documentation must include software artifacts, licenses, certificates and secure access arrangements, with responsibilities assigned for keeping them usable.

Third-party dependencies deserve the same attention. A provider’s availability commitment may not establish whether the enterprise can recover its own records, rebuild integrations or obtain urgent support during a widespread incident. Teams should examine contractual responsibilities alongside practical recovery options and test the handoffs they actually depend on.

Portability can help where the cost is justified, although moving a workload rarely removes its dependencies automatically. Rebuilding an application elsewhere still requires compatible data, keys and operational expertise. Leaders should approve alternative deployment options only when the full service can use them within an acceptable time and with adequate security.

Find the dependencies that spread disruption

An asset inventory identifies components. Resilience planning also needs to show how their failures affect business activity. Map the dependencies of each priority service, including authentication, name resolution, network connectivity, shared databases and external interfaces. Include administrative systems that staff need to investigate an incident and restore affected services.

The most useful maps expose concentrated reliance. Several apparently independent applications may share one identity provider, privileged access service or management platform. Geographical separation provides less protection when the same administrative account can modify both environments. Teams should examine which failures or compromises can cross their intended boundaries.

Combine discovery tools with architecture records and operational interviews. Network traffic shows some live dependencies, while application specialists may identify a monthly batch job that automated discovery misses. Validate the map through controlled exercises that remove a selected dependency and observe the effect on the business service.

Dependencies also change over time. A new API, supplier or security control can alter recovery requirements without changing the application’s name. Service maps should therefore be reviewed when material changes occur, with recovery procedures updated as part of the same approval. Their usefulness depends on remaining close to how the enterprise actually operates.

Make containment compatible with continuity

Segmentation should allow teams to contain a compromised component without unnecessarily disabling unrelated services. Design decisions need to address both data traffic and administrative access. A backup environment isolated from production workloads may still be exposed through shared privileged identities or a common management console.

NIST’s Zero Trust Architecture rejects implicit trust based solely on network location or asset ownership. Applied to resilience planning, this suggests that recovery access should have explicit authorization and verification. A secondary environment should not inherit trust merely because it sits in a different subnet or cloud account.

Organizations also need to determine how emergency access will work when their normal identity service is unavailable. Recovery credentials and key access should be securely controlled, independently usable where necessary and exercised under realistic conditions. Otherwise, the mechanism intended to protect recovery can itself prevent authorized teams from starting it.

Design controlled degradation

Keeping every critical service fully available throughout every attack is an unrealistic universal promise. Some incidents require an intentional shutdown to protect people, transactions or sensitive information. Architecture should support an agreed minimum service and safe suspension of functions that cannot operate reliably under compromised conditions.

Useful options include read-only access, delayed processing, alternate communications and carefully controlled manual procedures. Each brings tradeoffs. Queued transactions require reconciliation; manual activity needs oversight; stale information may be unsuitable for high-consequence decisions. These implications should be evaluated with business owners before an incident forces improvised choices.

Recovery time objectives should include the time needed to establish trust and validate service behavior. Starting the clock only when a restore command runs leaves significant disruption unmeasured. Track the complete interval through containment decisions, environment preparation and the point at which the business can perform its agreed minimum operations.

Make resilience part of the investment case

Leaders should compare proposed controls against specific disruption scenarios. Would independent administration prevent one compromised account from affecting every copy? Would an alternative order workflow reduce lost sales while core systems recover? Would rebuilding a shared identity service shorten the recovery path for several critical applications?

This approach helps distinguish necessary redundancy from expensive duplication. Additional infrastructure creates value when it addresses a tested dependency or business requirement. It can also create configuration drift, operational complexity and another environment to secure. The architecture decision should account for these ongoing obligations rather than treating duplication as an automatic improvement.

Funding must include maintenance and exercises. A recovery design gradually loses credibility if nobody updates deployment artifacts, verifies supplier contacts or practices the decision to isolate a service. Assign those activities to normal operational ownership, with evidence available to the service owner and executive risk forums.

This also changes how enterprises evaluate modernization. Removing an application from a data center does not establish that its business service has become more resilient. A migration may reduce one infrastructure exposure while increasing reliance on a shared cloud administration layer. The investment review should compare the service’s disruption scenarios before and after the change, including how teams would regain trusted control. Modernization creates a resilience benefit when the new design improves an identified capability and the organization can demonstrate that improvement through a relevant test.

The next architecture review

Executives can make progress by selecting one critical service and asking its owners to demonstrate how it would operate with compromised privileged access and an unavailable dependency. The exercise should reveal what can continue safely, what must stop and which assumptions require further investment.

The resulting priorities may involve identity, application behavior or supplier arrangements as much as backup capacity. Addressing those priorities gives cyber resiliency a concrete business purpose. The enterprise builds the ability to sustain an acceptable service through disruption and recover the rest with decisions, dependencies and responsibilities already understood.

← All articles

What this article says

More in Software Development

All →
Teladoc Health Expands Comprehensive Weight Care Program with Employer Contribution Option for GLP-1 Medications
Teladoc Health

Teladoc Health Expands Comprehensive Weight Care Program with Employer Contribution Option for GLP-1 Medications

L3Harris and Partners Demonstrate Multi-Domain Capabilities at EVEREST: Pacific Vigilance
L3Harris

L3Harris and Partners Demonstrate Multi-Domain Capabilities at EVEREST: Pacific Vigilance

Add interactivity to Canva presentations with Kahoot! 360
Kahoot

Add interactivity to Canva presentations with Kahoot! 360

Transform Canva presentations into Kahoot! lessons and study sessions
Kahoot

Transform Canva presentations into Kahoot! lessons and study sessions

The hidden cost of contactless care
HCLTech

The hidden cost of contactless care

Choosing an enterprise service management solution: Capabilities, platforms and selection criteria
HCLTech

Choosing an enterprise service management solution: Capabilities, platforms and selection criteria

More from HCLTech

The hidden cost of contactless care
HCLTech

The hidden cost of contactless care

Choosing an enterprise service management solution: Capabilities, platforms and selection criteria
HCLTech

Choosing an enterprise service management solution: Capabilities, platforms and selection criteria

Entitlement Server: The service exposure layer for devices
HCLTech

Entitlement Server: The service exposure layer for devices

HCLTech and Cohere partner to build and deliver sovereign AI
HCLTech

HCLTech and Cohere partner to build and deliver sovereign AI

Edge AI at scale: Making operational outcomes repeatable
HCLTech

Edge AI at scale: Making operational outcomes repeatable

Modernizing global customer support through cloud contact centers
HCLTech

Modernizing global customer support through cloud contact centers