rzo1 commented on code in PR #38: URL: https://github.com/apache/stormcrawler-site/pull/38#discussion_r2333309643
########## security/index.html: ########## @@ -0,0 +1,62 @@ +--- +layout: default +slug: security +title: Reporting Security Problems to Apache StormCrawler +--- + +<div class="row row-col"> + <h1>Security</h1> + <h2>Reporting New Security Problems with Apache StormCrawler</h2> + <p>The Apache Software Foundation takes a very active stance in eliminating security problems and denial of service attacks against its products.</p> + <p>We strongly encourage people to report security problems privately using the security mailing list of the <a href="https://www.apache.org/security/";>ASF Security Team</a> before disclosing them in a public forum.</p> + <p>Please note that the security mailing list should only be used for reporting undisclosed security vulnerabilities and managing the process of fixing such vulnerabilities. We cannot accept regular bug reports or other queries at this address. All mail sent to this address that does not relate to an undisclosed security problem in our source code will be ignored.</p> + <p>The private security mailing address is: <a class="externalLink" href="mailto:secur...@stormcrawler.apache.org";>secur...@stormcrawler.apache.org</a></p> + + <h2>Threat Model and Security Considerations</h2> + <p>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.</p> Review Comment: ```suggestion <p>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.</p> ``` ########## security/index.html: ########## @@ -0,0 +1,62 @@ +--- +layout: default +slug: security +title: Reporting Security Problems to Apache StormCrawler +--- + +<div class="row row-col"> + <h1>Security</h1> + <h2>Reporting New Security Problems with Apache StormCrawler</h2> + <p>The Apache Software Foundation takes a very active stance in eliminating security problems and denial of service attacks against its products.</p> + <p>We strongly encourage people to report security problems privately using the security mailing list of the <a href="https://www.apache.org/security/";>ASF Security Team</a> before disclosing them in a public forum.</p> + <p>Please note that the security mailing list should only be used for reporting undisclosed security vulnerabilities and managing the process of fixing such vulnerabilities. We cannot accept regular bug reports or other queries at this address. All mail sent to this address that does not relate to an undisclosed security problem in our source code will be ignored.</p> + <p>The private security mailing address is: <a class="externalLink" href="mailto:secur...@stormcrawler.apache.org";>secur...@stormcrawler.apache.org</a></p> + + <h2>Threat Model and Security Considerations</h2> + <p>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.</p> + + <h3>Trusted Configuration</h3> + <p>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.</p> + <p>If an attacker is able to modify this file, they would already have full access to the system, including:</p> + <ul> + <li>The ability to alter behavior of the topology</li> + <li>Access to credentials and other secrets</li> + <li>Arbitrary control over job execution</li> + </ul> + <p>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.</p> + + <h3>Storm Cluster Security</h3> + <p>StormCrawler runs on an Apache Storm cluster, which is designed to allow users to:</p> + <ul> + <li>Submit topologies</li> + <li>Execute custom, user-defined code</li> + </ul> + <p>This model inherently trusts cluster users and assumes they are authorized.</p> + + <h4>Security Recommendations:</h4> + <ul> + <li>Access to the Storm cluster must be strictly restricted to trusted users</li> Review Comment: ```suggestion <li>Access to the Apache Storm® cluster must be strictly restricted to trusted users</li> ``` ########## security/index.html: ########## @@ -0,0 +1,62 @@ +--- +layout: default +slug: security +title: Reporting Security Problems to Apache StormCrawler +--- + +<div class="row row-col"> + <h1>Security</h1> + <h2>Reporting New Security Problems with Apache StormCrawler</h2> + <p>The Apache Software Foundation takes a very active stance in eliminating security problems and denial of service attacks against its products.</p> + <p>We strongly encourage people to report security problems privately using the security mailing list of the <a href="https://www.apache.org/security/";>ASF Security Team</a> before disclosing them in a public forum.</p> + <p>Please note that the security mailing list should only be used for reporting undisclosed security vulnerabilities and managing the process of fixing such vulnerabilities. We cannot accept regular bug reports or other queries at this address. All mail sent to this address that does not relate to an undisclosed security problem in our source code will be ignored.</p> + <p>The private security mailing address is: <a class="externalLink" href="mailto:secur...@stormcrawler.apache.org";>secur...@stormcrawler.apache.org</a></p> + + <h2>Threat Model and Security Considerations</h2> + <p>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.</p> + + <h3>Trusted Configuration</h3> + <p>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.</p> + <p>If an attacker is able to modify this file, they would already have full access to the system, including:</p> + <ul> + <li>The ability to alter behavior of the topology</li> + <li>Access to credentials and other secrets</li> + <li>Arbitrary control over job execution</li> + </ul> + <p>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.</p> + + <h3>Storm Cluster Security</h3> Review Comment: ```suggestion <h3>Apache Storm® Cluster Security</h3> ``` ########## security/index.html: ########## @@ -0,0 +1,62 @@ +--- +layout: default +slug: security +title: Reporting Security Problems to Apache StormCrawler +--- + +<div class="row row-col"> + <h1>Security</h1> + <h2>Reporting New Security Problems with Apache StormCrawler</h2> + <p>The Apache Software Foundation takes a very active stance in eliminating security problems and denial of service attacks against its products.</p> + <p>We strongly encourage people to report security problems privately using the security mailing list of the <a href="https://www.apache.org/security/";>ASF Security Team</a> before disclosing them in a public forum.</p> + <p>Please note that the security mailing list should only be used for reporting undisclosed security vulnerabilities and managing the process of fixing such vulnerabilities. We cannot accept regular bug reports or other queries at this address. All mail sent to this address that does not relate to an undisclosed security problem in our source code will be ignored.</p> + <p>The private security mailing address is: <a class="externalLink" href="mailto:secur...@stormcrawler.apache.org";>secur...@stormcrawler.apache.org</a></p> + + <h2>Threat Model and Security Considerations</h2> + <p>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.</p> + + <h3>Trusted Configuration</h3> + <p>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.</p> + <p>If an attacker is able to modify this file, they would already have full access to the system, including:</p> + <ul> + <li>The ability to alter behavior of the topology</li> + <li>Access to credentials and other secrets</li> + <li>Arbitrary control over job execution</li> + </ul> + <p>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.</p> + + <h3>Storm Cluster Security</h3> + <p>StormCrawler runs on an Apache Storm cluster, which is designed to allow users to:</p> Review Comment: ```suggestion <p>StormCrawler runs on an Apache Storm® cluster, which is designed to allow users to:</p> ``` ########## security/index.html: ########## @@ -0,0 +1,62 @@ +--- +layout: default +slug: security +title: Reporting Security Problems to Apache StormCrawler +--- + +<div class="row row-col"> + <h1>Security</h1> + <h2>Reporting New Security Problems with Apache StormCrawler</h2> + <p>The Apache Software Foundation takes a very active stance in eliminating security problems and denial of service attacks against its products.</p> + <p>We strongly encourage people to report security problems privately using the security mailing list of the <a href="https://www.apache.org/security/";>ASF Security Team</a> before disclosing them in a public forum.</p> + <p>Please note that the security mailing list should only be used for reporting undisclosed security vulnerabilities and managing the process of fixing such vulnerabilities. We cannot accept regular bug reports or other queries at this address. All mail sent to this address that does not relate to an undisclosed security problem in our source code will be ignored.</p> + <p>The private security mailing address is: <a class="externalLink" href="mailto:secur...@stormcrawler.apache.org";>secur...@stormcrawler.apache.org</a></p> + + <h2>Threat Model and Security Considerations</h2> + <p>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.</p> + + <h3>Trusted Configuration</h3> + <p>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.</p> + <p>If an attacker is able to modify this file, they would already have full access to the system, including:</p> + <ul> + <li>The ability to alter behavior of the topology</li> + <li>Access to credentials and other secrets</li> + <li>Arbitrary control over job execution</li> + </ul> + <p>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.</p> + + <h3>Storm Cluster Security</h3> + <p>StormCrawler runs on an Apache Storm cluster, which is designed to allow users to:</p> + <ul> + <li>Submit topologies</li> + <li>Execute custom, user-defined code</li> + </ul> + <p>This model inherently trusts cluster users and assumes they are authorized.</p> + + <h4>Security Recommendations:</h4> + <ul> + <li>Access to the Storm cluster must be strictly restricted to trusted users</li> + <li>Underlying systems should not store secrets or hold elevated privileges beyond those assigned to the authorized users</li> + <li>Avoid deploying StormCrawler in multi-tenant environments without strong isolation guarantees</li> + </ul> + + <h3>Summary</h3> + <p>StormCrawler's security model assumes a trusted deployment environment. Users should:</p> + <ul> + <li>Secure configuration files and deployment infrastructure</li> + <li>Restrict Storm cluster access</li> Review Comment: ```suggestion <li>Restrict Apache Storm® cluster access</li> ``` -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
