How l4rm4nd/securethejuice works
• External Clients: Represent users (and potential attackers) connecting via a browser or SSH.
• Traefik Reverse Proxy: Acts as the entry point, terminating SSL, managing HTTP challenges, and routing requests based on domain names (e.g., juice.fictive.local, auth.fictive.local, traefik.fictive.local).
• Authelia: The authentication/authorization service that handles SSO – it uses its configuration files under authelia/config.
• OWASP Juice Shop: The main web application that requires pre-authentication via Authelia.
• Cowrie SSH Honeypot: A deceptive service set to capture SSH intruder activity, with configuration files found in the cowrie directory.
Relationships and Interactions Between Components
• Traefik routes web traffic based on the requested subdomain:
• Requests for juice.fictive.local are directed to the Juice Shop container.
• Requests for auth.fictive.local go to the Authelia container.
• Requests for traefik.fictive.local are routed to Traefik’s dashboard (with access restrictions).
• Authelia sits in front of Juice Shop so that once a user is authenticated via Authelia, they can access the application.
Architectural Patterns and Design Principles
• Reverse Proxy/Security Gateway: Traefik is central to traffic management, using SSL/TLS termination and routing logic based on host headers.
• Single-Sign-On (SSO) Mechanism: The authentication flow through Authelia should be clearly indicated.
• Honeypot Strategy: Cowrie is specifically set up to act as a decoy, capturing unauthorized SSH attempts.
• Use of Configuration Files: Emphasize that customization is done via config files (e.g., authelia/config/configuration.yml, cowrie/config.cfg, traefik/fileConfig.yml).
Relevant Technologies and Frameworks
• Docker and Docker Compose (see docker-compose.yml) to describe container orchestration.
• Traefik (for SSL reverse proxy).
• Authelia (for SSO and access control).
• OWASP Juice Shop (the target web app).
• Cowrie (for SSH honeypot deployment).
Elements
• All the key components (Traefik, Authelia, Juice Shop, Cowrie, and the Docker infrastructure) should be clearly labeled.
• Traffic incoming from the internet to Traefik.
• Authenticated web traffic routed from Traefik to Authelia and then to Juice Shop.
• A separate path mapping SSH connections directly to Cowrie on port 2222.
• Configuration dependencies in your annotations (e.g., adjustments in traefik/fileConfig.yml, authelia/configuration.yml, and cowrie config files).
This systematic approach to diagramming will ensure that you capture all the essential architectural elements of “SecureTheJuice” accurately.