FedNet infrastructure is engineered with redundancy and failover mechanisms to ensure high resilience against hardware failures or network disruptions.

Yes, FedNet services and features are designed to be flexible and adaptable accommodating changes over time.

Any operating system that can be virtualized can be deployed by the entity.

FedNet disaster recovery strategy encompasses a combination of redundant infrastructure, data replication, backup solutions, and rigorous testing procedures.

currently does not support physical machines.

Entities can define their own backup policy.

Yes, the backup data can be replicated to an additional site.

Yes, depending on the service opted for.

Yes, FedNet offers scalable bandwidth options to accommodate fluctuations in traffic volume.

With A robust DDoS protection mechanism that includes traffic analysis and automatic threat mitigation

Yes.

Service Availability SLA 99.9%

Incidents SLA:

Percentage of Severity 1 incidents successfully resolved within 4 hours (99.0%)

Percentage of Severity 2 incidents successfully resolved within 8 hours (99.0%)

Percentage of Severity 3 incidents successfully resolved within 4 calendar days (99.0%)

Percentage of Severity 4 incidents successfully resolved within 5 calendar days (99.0%)

Note: Time spent waiting for the entity's response will not be counted i.e. Stopwatch will be temporarily stopped.

are automatically registered in the SLAs and can access FedNet services after migration.

Yes, entities can use the existing subnet. However, to onboard FedNet, they must follow the FedNet IP scheme.

No, it is currently not available.

Yes, an access control policy and process are in place, and is granted only on a need-to-know basis.