Secure Launch (Pre-release/Pre-peak season diagnostics)

Beyond Service Guide

Will it fail? Will it leak? Will it be operational?

We will quickly assess load, security, and operational risks and submit a prioritized report

Available for short-term, one-off use
Based on actual measurements, including load testing
Prioritized improvement report

Secure Launch image

\ Response within one business day at the earliest /

Get started with a free consultation

WHAT IT IS

About the service

Secure Launch is a diagnostic service that quickly identifies and prioritizes the load, security, and operational risks of a web service, especially just before a launch or peak season .

It's not just about visually checking the configurationWe define the expected access volume numerically and then actually apply a load to verify whether it can withstand itEngineers whose main job is building cloud infrastructure and providing 24/7/365 operation and maintenance will review it from a practical perspective

* The scope and duration of the diagnosis will vary depending on the configuration and scale of the target system. We will discuss and determine the feasible scope of the diagnosis by working backward from the planned release date

Differences from general diagnostic services

- Vulnerability assessment service One-time use of load testing tools Secure Launch
Scope of diagnosis △ Only app vulnerabilities △ Load only ◎ Cross-cutting load, security, and operations
Person who will implement it △ Primarily automated detection using tools × Implemented in-house ◎ Confirmed by the person responsible for construction and operation
Stress testing × Not applicable ○ Can be implemented ◎ From design to implementation and retesting
Monitoring and backup × Not applicable × Not applicable ◎ Check the setup and recovery procedures
Report format △ List of detection results △ Numerical report ◎ Prioritized improvement suggestions
Improvement after diagnosis × Not applicable × Not applicable ◎ We can handle modifications and operations if necessary

* The two columns on the left summarize the general trends in service models. Actual service coverage may vary depending on the company

WISSUES

Isn't this the perfect timing ?

  • We will be launching a new web service soon
  • A surge in access is expected at the start of the new fiscal year
  • We have a major event/campaign coming up
  • We are preparing to revamp our existing services
  • Development and infrastructure are handled by separate companies, so there's no one to oversee the whole picture
  • They're releasing it without checking if it can withstand the load
  • I'm worried about whether my monitoring and backup settings are correct
  • There are no established procedures for when a problem occurs

SERVICE

Diagnosis

01Application Configuration Review: Check the implementation, dependencies, and computationally intensive areas.
02Cloud Configuration Review: Check redundancy, scaling settings, and single point of failure.
03Checking Database Load:Check slow queries, indexes, and connection limits.
04for the load testnumerically and create a test plan.
05Load Testing: Wewill use Apache JMeter to apply a load simulating the production environment and perform verification.
06WAF Configuration Check:Check the detection rules, exclusion settings, and log acquisition status.
07Authentication and Permissions Check:We will check the access routes, permission design, and exposure of the management screen.
08Checking Monitoring Settings:Verify that the monitoring targets, thresholds, and notification paths match the actual situation.
09 Verify that the backup contents and recovery procedures actually work .
10.Check the incident response flow:Verify that it is determined who will do what.
11.Create an improvement report.Summarize the risks and priorities in one document.

* The scope of the testing will be adjusted depending on the time remaining until the scheduled release date. We can also handle short-term configuration checks without load testing

A REPORT IN PRACTICE

Actualdiagnostic report

  • ▶Items checked and results
  • ▶List of identified risks (organized by impact and likelihood of occurrence)
  • ▶Priority of action (immediately / before release / after release)
  • ▶Suggestions for specific improvement methods
  • ▶Evaluation of resilience to production access (including load testing)
Diagnostic report (image)
currentlybelow the expected peak.
There is now a way to access the admin panel without authentication
before releaseshowed response delays from approximately 60% of the target throughput.
The backup recovery procedure has not yet been verified before release
post-publicationmonitoring do not reflect the actual situation.
The person responsible for the post-release incident response flow has not yet been determined

*The displayed content is for illustrative purposes only

OUTCOME

What changes after receiving a diagnosis ?

01

to the release datewithout any worries.

You'll no longer go into the actual event with a "it'll probably be okay" attitude. Because you define the expected access numerically and then actually apply the load,You can go into the release date knowing how many people it can handle
02

The order in which things need to be fixedbecomes clear.

A report that simply lists risks doesn't tell you where to start. It should be organized by impact and probabilityWe will present it in three stages: now, before release, and after release
03

If there are no problems,I will let you know.

We will not use the diagnosis as a pretext to make additional suggestions. If there are no major problems at present, we will simply tell you that "there are no problems."We will never recommend unnecessary renovations or contracts

NEXT STEP

What to do after the diagnosis ?

If there are significant challenges in design or implementation, we propose modifications and redesigns using Secure Build (secure development )
If you require a system for continuous monitoring , we recommend our Secure AppOps monthly management service
If the improvements are standard and a package solution suffices , we will propose a combination of our own online reservation system "EDISONE" and customized solutions
If there are no major problems at present, we will not make any suggestions and will simply tell you "There are no problems." We will not recommend unnecessary renovations or contracts.

CONTACT

Please let us know your planned release date.

We will ask about your planned release date and expected access volume, and then provide you with an estimate of the scope of our diagnostics and a schedule

Consult about the diagnosis