gighive

GigHive Security Overview

This document summarizes the primary security controls implemented in the GigHive stack and how to configure them per environment.

Highlights (Most to Least Critical)

Protected Paths

Auth is enforced by Apache for the following URI prefixes:

To protect an additional path (e.g., /upload), add a block to default-ssl.conf.j2:

<LocationMatch "^/upload(?:/|$)">
  AuthType Basic
  AuthName "GigHive Protected"
  AuthBasicProvider file
  AuthUserFile {{ gighive_htpasswd_path }}
  Require valid-user
</LocationMatch>

Environment & Configuration

Example in group_vars/gighive.yml:

filename_seq_pad: 5
upload_max_bytes: 1500000000

.env.j2 wires them through to the container environment.

PHP/Apache Integration

WAF Notes

Dependency Management

Hardening Checklist (Per Environment)

File/Path References

Reporting Security Issues

Please report suspected vulnerabilities privately to the repository owner/maintainers. Provide:

We will acknowledge receipt and work on a fix with an appropriate disclosure timeline.