[FLINK-36889] Mention locking down a Flink cluster in the 'Production Readiness Checklist' #25793
Conversation
… Readiness Checklist'
| ### Secure Flink Cluster Access | ||
|
|
||
| To prevent potential security vulnerabilities, such as arbitrary code execution, ensure that your Flink clusters are only accessible to trusted users. Flink clusters should not be exposed to the company intranet or public internet. For more details, refer to the [Flink Security FAQ](https://flink.apache.org/what-is-flink/security/#during-a-security-analysis-of-flink-i-noticed-that-flink-allows-for-remote-code-execution-is-this-an-issue). |
There was a problem hiding this comment.
it seems very restrictive to say Flink clusters should not be exposed to the company intranet. If they are locked down with TLS and appropriate authentication - this could be acceptable, rather than having to have its own network to run Flink. We could have a statement around TLS and better still mTLS for all connections.
There was a problem hiding this comment.
Thank you @davidradl.
i have incorporated your suggestion. Please review whenever time
|
Reviewed by Chi on 12/12/24. Asked submitter questions |
|
@rmetzger Please review whenever time |
| ### Secure Flink Cluster Access | ||
|
|
||
| To prevent potential security vulnerabilities, such as arbitrary code execution, |
There was a problem hiding this comment.
I think the language here can be more explicit. Arbitrary code execution is not a potential vulnerability.
Flink has been designed for arbitrary, remote code execution -- it is not an accident ;)
Check also this FAQ entry for how we've worded this in the past: https://flink.apache.org/what-is-flink/security/#during-a-security-analysis-of-flink-i-noticed-that-flink-allows-for-remote-code-execution-is-this-an-issue
What is the purpose of the change
Add a note section in
Production Readiness Checkliston flink securityBrief change log
just a doc update
Verifying this change
validate markdown file is rendered properly
Does this pull request potentially affect one of the following parts:
N/A
Documentation