Created comprehensive security hardening guide (500+ lines): Defense-in-Depth Strategy: - Layer 1: Fail2Ban auto-banning - Layer 2: SSH key-only authentication - Layer 3: UFW firewall optimization 5-Phase Deployment (1 hour total): - Phase 1: Test SSH key access (CRITICAL - prevents lockout) - Phase 2: Install and configure Fail2Ban (20 min) - Phase 3: SSH hardening (20 min) - Phase 4: UFW firewall review (15 min) - Phase 5: Additional security (automatic updates, AIDE) Security Features: - Fail2Ban monitors SSH, Nginx, bad bots - SSH: Key-only auth, MaxAuthTries=3, rate limiting - UFW: Management IP whitelist, unnecessary ports closed - Automatic security updates - File integrity checking (AIDE) Critical Safety Measures: - Mandatory SSH key testing before disabling passwords - Keep session open while testing - Backup access via console/IPMI - Step-by-step verification at each phase - Comprehensive troubleshooting (lockout recovery) Monitoring & Maintenance: - Daily: Check Fail2Ban bans and auth logs - Weekly: Review UFW logs and security updates - Monthly: AIDE file integrity check Ready to deploy when SSH access available. Risk level: MEDIUM (can lock out if keys not tested) Task: Command Center Security Hardening (Tier 1) FFG-STD-002 compliant
133 lines
3.5 KiB
Markdown
133 lines
3.5 KiB
Markdown
# Staff Recruitment Launch
|
|
|
|
**Status:** DOCUMENTATION COMPLETE - Ready to Post
|
|
**Owner:** Michael "Frostystyle" Krause
|
|
**Priority:** Tier 0 - Immediate Win
|
|
**Last Updated:** 2026-02-17
|
|
**Time Estimate:** 30 min (finalize) + 2-3 hours (post & manage)
|
|
|
|
---
|
|
|
|
## Overview
|
|
|
|
Launch recruitment campaign for Builders (2-3) and Social Media Helper (1) to support Firefrost Gaming launch.
|
|
|
|
---
|
|
|
|
## What It Is
|
|
|
|
Coordinate the recruitment of founding staff members using the Discord recruitment ad created by The Guardian. Includes provisioning incentive instances (private servers) for recruits and managing the application process.
|
|
|
|
---
|
|
|
|
## Prerequisites (Guardian's Notes)
|
|
|
|
Before posting the recruitment ad, ensure:
|
|
|
|
1. **Incentive instances ready to provision**
|
|
- Private dedicated Minecraft servers for recruits
|
|
- Resource allocation defined (CPU/RAM)
|
|
- Hosting plan confirmed
|
|
|
|
2. **Application process defined**
|
|
- How will applications be received? (Discord DM, form, etc.)
|
|
- Who reviews applications?
|
|
- Interview/vetting process
|
|
|
|
3. **Recruitment ad finalized**
|
|
- Decision: Mention specific modpacks or keep general?
|
|
- Consider: Application deadline? (optional)
|
|
- Location: `docs/planning/discord-recruitment-ad.md`
|
|
|
|
---
|
|
|
|
## Success Criteria
|
|
|
|
- [ ] Incentive instances provisioned and ready
|
|
- [ ] Application process documented
|
|
- [ ] Recruitment ad posted to target channels
|
|
- [ ] 2-3 qualified Builder applicants received
|
|
- [ ] 1 qualified Social Media Helper applicant received
|
|
- [ ] Selected candidates onboarded
|
|
|
|
---
|
|
|
|
## Implementation Steps
|
|
|
|
### Phase 1: Pre-Launch Setup (Before Posting)
|
|
|
|
1. **Provision Incentive Instances**
|
|
- Set up private Minecraft servers for recruits
|
|
- Document resource allocation
|
|
- Test server access and stability
|
|
|
|
2. **Define Application Process**
|
|
- Create application review checklist
|
|
- Set up tracking system (spreadsheet, etc.)
|
|
- Define interview questions
|
|
|
|
3. **Finalize Recruitment Ad**
|
|
- Review Guardian's draft: `docs/planning/discord-recruitment-ad.md`
|
|
- Make any final edits
|
|
- Decide on posting schedule
|
|
|
|
### Phase 2: Launch
|
|
|
|
1. **Post to Target Channels**
|
|
- r/feedthebeast (Reddit)
|
|
- r/feedthebeast Discord
|
|
- Other modded Minecraft communities
|
|
- Firefrost Discord (when established)
|
|
|
|
2. **Manage Applications**
|
|
- Review incoming applications
|
|
- Schedule interviews
|
|
- Check references/portfolios
|
|
|
|
3. **Select and Onboard**
|
|
- Make offers to selected candidates
|
|
- Grant access to incentive instances
|
|
- Provide onboarding documentation
|
|
|
|
---
|
|
|
|
## Blocks
|
|
|
|
**This task blocks:**
|
|
- Spawn area design and build-out
|
|
- Social media launch campaign
|
|
- Community growth initiatives
|
|
|
|
**Blocked by:**
|
|
- None (ready when incentive instances are provisioned)
|
|
|
|
---
|
|
|
|
## Documentation
|
|
|
|
**Current directory contents:**
|
|
- `README.md` - This file (task overview)
|
|
|
|
**Related documents:**
|
|
- `docs/planning/discord-recruitment-ad.md` - Recruitment ad (created by The Guardian)
|
|
- `docs/planning/staff-recruitment-planning.md` - Original planning doc (archived)
|
|
- `docs/planning/emissary-social-media-handbook.md` - Social media role context
|
|
|
|
**Additional docs to create:**
|
|
- [ ] `prerequisites.md` - Incentive instance setup guide
|
|
- [ ] `application-process.md` - How to review and vet candidates
|
|
- [ ] `onboarding-checklist.md` - New staff onboarding steps
|
|
|
|
---
|
|
|
|
**Fire + Frost + Foundation = Where Love Builds Legacy** 💙🔥❄️
|
|
|
|
---
|
|
|
|
**Document Status:** ACTIVE
|
|
**Next Steps:**
|
|
1. Provision incentive instances
|
|
2. Define application review process
|
|
3. Finalize recruitment ad edits
|
|
4. Post to recruitment channels
|