[SECURITY] security(backend): Enforce HTTPS and Secure WSS WebSocket Protocol in Production

[chiscookeke11]

[SECURITY] security(backend): Enforce HTTPS and Secure WSS WebSocket Protocol in Production

Metadata

Field	Value
Domain	Security
Difficulty	Easy (1–2 Days)
Effort Estimate	effort: 2h
Priority	P2-Medium
Labels	good first issue, security
Target Branch	master
Depends On	None

🎯 Context & Goal

Financial gaming platforms handling decentralized cryptocurrency escrows demand top-tier security standards. In the security and performance domain, redirects http traffic to https and enforces encrypted wss connections for all websocket traffic. Implementing this security safeguard prevents unauthorized balance transfers, exploit vectors, and client-side tampering. This issue provides full remediation steps, target file paths, and test requirements targeting the master branch.

📂 Target Files

• backend/server.js

📋 Implementation Tasks

• Task: Implement security safeguard for security(backend): Enforce HTTPS and Secure WSS WebSocket Protocol in Production in backend/server.js.
• Task: Write exploit simulation test asserting vulnerability is blocked.
• Task: Verify zero regressions across existing functionality.

🛠️ Technical Guidance

Apply defense-in-depth principles and never trust client-supplied input without server verification.

🔗 References & Related

• Reference file: backend/server.js

⏳ Delivery Window

This issue should be completed within 1 day(s) of assignment.

Contribution Workflow

1. Branch off master: git checkout -b feature/descriptive-name master
2. Implement all tasks in the checklist above.
3. Run all CI checks locally (see DEVELOPMENT.md).
4. Open a Pull Request targeting master.
5. Link this issue in your PR description: Closes #143.

✅ Acceptance Criteria

• All implementation tasks listed above are fully completed.
• Code compiles and passes all local CI checks.
• PR targets master branch.
• PR description references this issue.