F2Cloud frequently asked questions

Cloud backup keeps protected copies of data and VM images. Disaster recovery uses those copies to run workloads in a prepared environment, together with network, firewall, VPN and traffic routing.

Protected capacity, retention, immutable copy requirements, workload count and restore-test frequency. After discovery we prepare a monthly service proposal.

The service includes integrity checks and scheduled restore tests, with results reported to you.

A backup copy that cannot be modified or deleted during the defined retention period, so it survives even if ransomware or unauthorised access targets your backups.

No. It doesn't prevent the attack; it ensures a reliable recovery point exists afterwards. Prevention needs layers such as EDR and segmentation.

Retention policies are defined together with you, based on business and regulatory needs.

Disaster Recovery as a Service runs your critical systems in a provider's prepared cloud environment during a disaster, delivered as a managed service.

For eligible, prepared and tested workloads, a target RTO down to 30 minutes can be designed. It isn't guaranteed for every system and is validated through exercises.

For many organisations the hardware, licence, connectivity and staffing cost of a second site exceeds a monthly DRaaS service. Decide based on critical workloads and target RTO/RPO.

Identify an unaffected, protected (ideally immutable) backup point, verify it in an isolated environment, then restore it.

Disaster recovery typically targets infrastructure or site loss. Cyber recovery adds verifying a trustworthy clean point when the data itself is in question.

Immutable backups, separated management identities, an isolated recovery environment and regular exercises are the core steps.

It varies with workload count, RTO/RPO targets, retention and required network and security services. We prepare a monthly proposal after discovery.

A second site requires hardware, licence, connectivity and staffing investment. For many organisations monthly DRaaS is more predictable; decide based on your workloads.

Source platform, workload count and criticality, target RTO/RPO and network dependencies. You never need to share access credentials or passwords.

Development, test, build and delivery infrastructure built and operated by a provider, isolated per team.

Yes. Your Git provider and CI tool are assessed during discovery and the integration is planned.

Yes. WebShield covers web and API workloads, and managed Kubernetes covers containerised production.

A service model where the provider handles cluster build-out, upgrades, monitoring and security operations.

Monthly, based on node resources, cluster count, storage, backup and security scope.

Namespace isolation, network policies, access control and, in supported environments, image scanning and runtime protection with Kaspersky Container Security.

The runners, registries, repositories and environments required to automatically build, test and deploy code changes.

On shared runners, one project's secrets or dependencies can affect another. Isolation reduces supply-chain risk.

Yes. Servers that distribute software updates to your customers can be hosted in the DevOps zone.

Hosting where traffic to your application passes through a protection layer that mitigates denial-of-service attacks.

DDoS mitigation typically addresses volumetric network-layer attacks. A WAF inspects application-layer attacks such as SQL injection and XSS. They complement each other.

Yes. SaaS platforms, customer portals and APIs can be hosted in WebShield.

A model where the provider handles WAF deployment, rule tuning, false-positive management and continuous monitoring.

Yes. Schema, rate-limit and attack-pattern policies can be applied to API endpoints.

Number of protected applications, traffic volume, WAF scope and monitoring level; we prepare a monthly proposal.

Combine trusted images, image scanning, namespace isolation, network policies, access control and runtime visibility.

EDR detects suspicious behaviour on the server and enables response, giving visibility beyond signature-based protection.

That depends on environment and compatibility; we assess it during discovery.

Not on its own. Data location is an important input, but legal grounds, security and actual data flows need separate assessment.