It is required. For backups, not only “taking” them but also “being able to restore” them is important, so we design them including recovery procedures and recovery testing.

Yes, it’s possible. Our basic approach is to integrate while leveraging your existing assets. We can also propose additions or enhancements only for the areas that are lacking.

Basically, the flow is: current state inventory → ideal state/prioritization → implementation for one target → incorporation into operations → horizontal rollout.

Configuration diagrams, monitoring design documents, backup design documents, notification/ticketing design, runbooks, recovery procedures, recovery test results, operations handover materials, etc.

Other deliverables depend on individual requirements.

Start small (1 target), create a success pattern, then scale horizontally. Since it varies by scale and requirements, we present a roadmap after As-is inventory.

Designed with the principles of least privilege, bastion/temporary credentials, operation logs, and procedure-based operations. Secret masking and environment isolation are also implemented as needed. 

Monitoring tools/notification destinations, backup methods/generations/storage locations, critical systems list, incident history, recovery challenges, network overview diagram (if available), etc. 

Custom quotes based on current scale (sites/units/monitored targets/backup capacity), existing tools, RPO/RTO requirements, and documentation scope. We also support spot, quasi-mandate, and ongoing operations support.