K06-broken-auth: Ingress object without TLS cert #57
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Creating an Ingress Object without TLS certificates can be a security concern, as it may lead to potential vulnerabilities and data exposure. While TLS can be used for encryption, TLS also provides a level of authentication by verifying the identity of the server to which a client is connecting. This is done through the server presenting a digital certificate signed by a trusted Certificate Authority (CA). The client can verify the certificate to ensure that it is connecting to the legitimate server and not an imposter. Sadly, I don't have access to any threat research report statistics on this matter, however, this is generally considered a bad practice and should be included in the report, I believe.