Policy document
OPSEC Guidelines
Ismaili Warrior Alliance
The rules governing what members may share, on which platforms, and how violations are handled.
How to read this document. Where this document says “Founding Circle”, it means the Alliance's founding members acting together: there is no board and no charter. The orientation, annual refresher, mentorship and peer support it names are member practices, not formal programs, and items marked “[To be established]” are not yet available. The classification line is the document's own and is reproduced as written. The rule on unit designations and deployment details binds members who are still serving; the profiles in the record are separated members, and each is published only with its member's recorded approval.
Doctrine adopted January 2025. Reproduced as written.
Contents
- Purpose
- Core OPSEC Principles
- 1. Assume All Communications Are Monitored
- 2. Protect Critical Information
- 3. Member Privacy Is Sacred
- Platform-Specific Guidance
- Signal Group
- LinkedIn Private Group
- External Communications
- Prohibited Topics (All Platforms)
- Foreign Contact and Travel
- Social Media OPSEC
- Consequences of OPSEC Violations
- What to Do If You See a Violation
- OPSEC Self-Audit
- Training and Awareness
- Additional Resources
- Acknowledgment
Purpose
These Operational Security (OPSEC) guidelines protect Alliance members, maintain mission integrity, and ensure compliance with federal law and military regulations.
Bottom line: If you wouldn't say it in a security brief, don't say it here.
Core OPSEC Principles
1. Assume All Communications Are Monitored
Even on encrypted platforms, practice discipline:
- Write as if a counterintelligence officer is reading
- No classified or sensitive information, period
- When in doubt, leave it out
2. Protect Critical Information
Never share:
- Unit designations (battalion, squadron, ship, etc.)
- Deployment locations, dates, or rotations
- Classified material or discussion of classified topics
- Security procedures or vulnerabilities
- Personnel movement or operational plans
- Technology specifications or capabilities
Acceptable:
- Branch of service (Army, Navy, USMC, USAF, USSF, USCG)
- General MOS/AFSC/Rating (e.g., "logistics officer," "intel analyst")
- Years of service or rank (without unit specifics)
- Professional development and transition topics
3. Member Privacy Is Sacred
Always required:
- Explicit consent before posting photos with identifiable members
- Permission before sharing someone's story or experience
- Anonymization when discussing outcomes or case studies
Default:
- First name only in group discussions
- No tagging members in public posts
- Private messages for sensitive topics
Platform-Specific Guidance
Signal Group
Security Level: HIGH
Use for:
- Day-to-day coordination
- Sensitive mentorship discussions
- Time-sensitive updates
- Private member support
Rules:
- Disappearing messages: 1 week default
- No screenshots without permission
- No forwarding to external contacts
- Verify all new members before adding
LinkedIn Private Group
Security Level: MODERATE
Use for:
- Professional networking and development
- Public-safe career discussions
- Resource sharing (articles, opportunities)
- Announcements and events
Rules:
- Assume LinkedIn monitors all content
- No OPSEC violations (see prohibited topics)
- Professional tone at all times
- Link to Signal for sensitive follow-ups
External Communications
Security Level: LOW (Public)
Use for:
- General information about the Alliance
- Public-safe content (creed, values, mission)
- Career transition resources
Rules:
- Founder approval required for all external statements
- No member names or photos without consent
- No operational details whatsoever
Prohibited Topics (All Platforms)
- Classified Information
- Anything marked CONFIDENTIAL, SECRET, TOP SECRET
- Controlled Unclassified Information (CUI)
- FOUO (For Official Use Only) material
- Operational Details
- Deployments (past, present, future)
- Unit locations or movements
- Mission specifics or tactics
- Security Procedures
- Access control methods
- Clearance processes
- Counterintelligence operations
- Technology & Capabilities
- Weapons systems specifications
- Intelligence collection methods
- Cyber operations or vulnerabilities
- Personnel Information
- Full names with ranks and units
- Home addresses or contact info
- Family member details
Foreign Contact and Travel
Requirement: If you are subject to foreign contact reporting requirements (security clearance holders), comply with your agency/branch regulations.
Best Practice:
- Inform Founding Circle if you will be traveling to high-risk countries
- Be mindful that Alliance membership may be of interest to foreign intelligence services
- Report suspicious inquiries about the Alliance or its members
Social Media OPSEC
General Rules:
- Do not list "Ismaili Warrior Alliance" on public profiles without vetting with leadership
- Do not post photos from Alliance events without member consent
- Do not tag members in ways that reveal military affiliation
- Review your privacy settings regularly
Red Flags:
- Geotagging locations
- Posting while on mission or deployment
- Revealing travel plans before they occur
- Connecting with unknown foreign nationals
Consequences of OPSEC Violations
| Severity | Description | Action |
|---|---|---|
| Low | Accidental minor slip (quickly corrected) | Private warning |
| Moderate | Repeated carelessness | Temporary suspension |
| High | Intentional or reckless sharing | Immediate removal |
| Critical | Classified disclosure | Removal + law enforcement |
Note: Federal law (18 U.S.C. § 798) makes unauthorized disclosure of classified information a criminal offense. The Alliance will cooperate fully with authorities if such violations occur.
What to Do If You See a Violation
- Do not engage publicly. Send a private message to the member if safe to do so.
- Report immediately to Founding Circle via Signal.
- Document (screenshot if necessary, then delete from your device after reporting).
- Do not share the violation with others outside of leadership.
Reporting Channel: [Secure Signal number to be established]
OPSEC Self-Audit
Before posting anything, ask:
- ✅ Would I say this in front of my commanding officer?
- ✅ Does this reveal operational details?
- ✅ Could this information be used against the U.S. or its allies?
- ✅ Am I protecting member privacy?
- ✅ Is this something I'd be comfortable seeing on the front page of a newspaper?
If you answer "no" to any of these, do not post.
Training and Awareness
New Member Orientation:
- All new members must acknowledge OPSEC guidelines before gaining full access
- Onboarding includes OPSEC scenario training
Ongoing:
- Annual OPSEC refresher for all members
- Leadership monitors for emerging threats and updates guidelines as needed
Additional Resources
DoD OPSEC:
Branch-Specific OPSEC:
- Army: AR 530-1
- Navy: SECNAVINST 3070.2
- Marine Corps: MCO 3070.2
- Air Force: AFI 10-701
- Coast Guard: COMDTINST M3070.1
Alliance Contact:
- Founding Circle via secure Signal channel
Acknowledgment
I have read and understand the Ismaili Warrior Alliance OPSEC Guidelines. I commit to:
- Protect classified and sensitive information at all times
- Maintain member privacy and security
- Report violations immediately
- Accept full responsibility for my communications
Signature (Digital): [Member name]
Date: [Date]
"Discipline protects. Silence shields. Trust is earned."
Strength in Service. Wisdom in Faith.
Version: 1.0
Last Updated: January 2025
Next Review: Quarterly