rzo1 opened a new issue, #36: URL: https://github.com/apache/stormcrawler-site/issues/36
Let’s add a security page to the website that includes content like the example below. ---- # Threat Model and Security Considerations StormCrawler is designed to operate in trusted environments as part of a distributed Apache Storm cluster. This document outlines the threat model and key security assumptions to help users understand the secure use and deployment of StormCrawler. --- ## Trusted Configuration The configuration file used by StormCrawler is loaded during topology submission and is treated as a **trusted source**. It does not involve any user-supplied input at runtime. If an attacker is able to modify this file, they would already have full access to the system, including: - The ability to alter behavior of the topology - Access to credentials and other secrets - Arbitrary control over job execution Securing the configuration file and the environment in which topologies are submitted is essential. However, modification of the file implies full system compromise and is out of scope for runtime protections. ## Storm Cluster Security StormCrawler runs on an **Apache Storm cluster**, which is designed to allow users to: - Submit topologies - Execute custom, user-defined code This model inherently trusts cluster users and assumes they are authorized. **Security Recommendations:** - Access to the Storm cluster must be **strictly restricted to trusted users** - Underlying systems should **not store secrets** or hold elevated privileges beyond those assigned to the authorized users - Avoid deploying StormCrawler in multi-tenant environments without strong isolation guarantees ## Summary StormCrawler's security model assumes a **trusted deployment environment**. Users should: - Secure configuration files and deployment infrastructure - Restrict Storm cluster access - Follow best practices for secret and privilege management -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@stormcrawler.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
