// tool reference · Governance & Advisory

Security Center Business

プラットフォームの防御態勢：ブロックリスト、ロックダウン、ハニーポット、レート制限の管理。

What it does

The platform's own defensive controls: IP/CIDR/ASN/country blocklists, lockdown mode, honeypot sensitivity and rate-limit posture.

When to use it

You are under active abuse and need to tighten posture now.
Reviewing what is currently blocked and why.

Inputs

Field names are the actual form parameters, verified against source.

Field	種類	Required	Notes
tab	select	任意	Which control surface.
ip	text	任意	Address to block or inspect.
blocked_cidrs	textarea	任意	CIDR blocklist.
blocked_asns	textarea	任意	ASN blocklist.
blocked_countries	textarea	任意	Country blocklist.
lockdown	checkbox	任意	Lockdown mode.
honeypot_sensitive	checkbox	任意	Honeypot sensitivity.
rate_limit_posture	select	任意	Global rate-limit posture.

What you get back

Current posture, active blocks, and recent security events.

活用例

Input

tab = blocklist   blocked_cidrs = 198.51.100.0/24   lockdown = off

Output (abridged)

POSTURE UPDATED

  Blocked CIDRs      1  (198.51.100.0/24)
  Blocked ASNs       0
  Blocked countries  0
  Lockdown           off
  Honeypot           standard
  Rate-limit posture normal

  Effective immediately.

CAUTION: country and ASN blocks are blunt. A country block removes
legitimate users and a VPN defeats it in one click. Prefer a CIDR or
an ASN block scoped to the actual abuse.

How it works

Deterministic. Changes take effect on the next request — there is no cache to wait for.

Limits

Read live from the platform configuration.

Rate limit

30 requests / 60s (platform default)

Limitations — what it does なし do

Application-layer defence. It cannot absorb a volumetric DoS that never reaches PHP — that needs an edge WAF/CDN. A country block is easily bypassed with a VPN while permanently excluding real users.

プライバシー

Blocklists and security events are stored. Actor identity is pseudonymised in event data.

Standards

NIST CSF (PR.AC, DE.CM)OWASP