When to call us

Microsoft 365 or Google Workspace still on its initial settingsDefaults favour convenience, not safety.
Admin accounts are not under controlWho is an admin, is MFA on, are leavers' accounts gone.
AWS or Azure is left to developers or a vendorNobody independent has checked exposure, IAM, logging and network basics.
You must meet head-office or customer cloud standardsThe gap against CIS benchmarks or group policy.
Several clouds, no overall pictureM365, AWS and Google Workspace checked in one pass.
You want to know when settings drift backSecureWatch can watch the important settings after the review.

What is checked

  • Microsoft 365 / Entra ID:MFA and conditional access, admin roles, legacy authentication, external sharing, mail forwarding, app consents, audit log retention, Defender settings.
  • Google Workspace:2-step verification enforcement, admin roles, external sharing, less secure apps, audit logs, Gmail forwarding and delegation.
  • AWS:Root account, IAM users and roles, MFA, public S3 buckets, security groups, CloudTrail and GuardDuty, backups.
  • Azure:Subscription permissions, storage exposure, NSGs, activity logs, Defender for Cloud.
  • Standards:Checked against CIS benchmarks and, where needed, your group's or customer's standard.

Settings drift. New users, new services and vendor work change configuration after any review. We recommend watching the important settings with SecureWatch afterwards.

How an engagement runs

  1. Configuration reviewWith read-only access we review tenant and account settings. Nothing in production is changed.
  2. Logging reviewAudit and activity logs: enabled, retention period, alerting.
  3. PrioritisationItems ranked by impact, likelihood, effort and effect on daily work.
  4. Remediation supportStep-by-step fixes; we can make the changes for you, recording before and after.
  5. MonitoringIf you want it, SecureWatch watches the reviewed settings for changes.

Deliverables

  • Assessment report in English, Japanese or both: current state, recommended setting, steps and business impact per item
  • Management summary
  • Prioritised fix list
  • Post-fix verification
  • Mapping to CIS or your group standard where needed

Indicative pricing

Starting pointFrom about JPY 350,000Indicative for one tenant (Microsoft 365 or Google Workspace) or one AWS or Azure account. The price depends on the number of tenants and accounts and the remediation support you want. Scope and price are fixed before work starts.

Frequently asked questions

What does it cost?

One tenant or one account starts at about JPY 350,000. The price depends on the number of tenants and accounts and how much remediation support you want.

What access do you need?

Temporary read-only roles, such as Global Reader in Microsoft 365 or ReadOnlyAccess in AWS. You can remove them when the review is done.

Will the fixes disrupt work?

Enforcing MFA or disabling legacy authentication can affect older applications and devices. The report flags the likely effect per item and proposes a staged rollout.

How is this different from a vulnerability assessment?

A vulnerability assessment looks at servers and websites from outside. A cloud assessment looks at the configuration of cloud services from inside. They are often combined.

Can you work in both English and Japanese?

Yes. Meetings, reports and management briefings are available in English and Japanese, so a foreign head office and the Japanese team can work from the same findings.

How often should it be repeated?

After major changes or once a year. For continuous checking, SecureWatch can monitor the important settings.

Tell us which clouds you use and we will send the checklist and the price.

Microsoft 365, Google Workspace, AWS or Azure, and how many tenants and accounts: that is enough to scope it.

Contact