ENGAGEMENT_RULES

The mission objective is logical exploitation, not resource exhaustion. Any attempt to perform Layer 7 DDoS, volume-based flooding, or local resource exhaustion against BIT-SEC-CON infrastructure is strictly forbidden.

The mainframe is monitored by the Security Sentinel. Any script-based flag submission (spamming), unauthorized identity spoofing, or manipulation of the mission vault will result in an immediate ACCESS_REVOKED (System Ban).

Operators must strictly adhere to the provided mission perimeter. Attacks on third-party integration nodes (Luma, YouTube, or AWS Infrastructure) are strictly prohibited and will be reported to National Cyber Defense units.

BIT-SEC-CON 0x2 is a controlled simulation. Use of malware, ransomware, or persistent backdoors in any shared environments (if applicable) is grounds for permanent disqualification and legal escalation.

If you discover a critical vulnerability in the BIT-SEC-CON platform itself (not the CTF challenges), report it to the Core Collective via the secure Discord channel. Exploiting platform-level bugs is considered cheating.

Operators must use a unique handle. Impersonating conference staff, speakers, or other operatives to gain tactical advantages will result in the severing of your network uplink.