Skip to content

doc: Update threat model to treat untrusted upstreams and downstreams equally#14758

Merged
yanavlasov merged 5 commits intoenvoyproxy:mainfrom
yanavlasov:threat-model-update
Jan 30, 2021
Merged

doc: Update threat model to treat untrusted upstreams and downstreams equally#14758
yanavlasov merged 5 commits intoenvoyproxy:mainfrom
yanavlasov:threat-model-update

Conversation

@yanavlasov
Copy link
Contributor

Risk Level: Low
Testing: N/A
Docs Changes: Yes
Release Notes: N/A
Platform Specific Features: N/A
Fixes #12278

Signed-off-by: Yan Avlasov yavlasov@google.com

…eams

Signed-off-by: Yan Avlasov <yavlasov@google.com>
mattklein123
mattklein123 previously approved these changes Jan 20, 2021
Copy link
Member

@mattklein123 mattklein123 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM assuming we feel we are ready to flip to "enforcing!" Nice work!

asraa
asraa previously approved these changes Jan 21, 2021
Copy link
Contributor

@asraa asraa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@envoyproxy/security-team

htuch
htuch previously approved these changes Jan 22, 2021
Copy link
Member

@htuch htuch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. This is a huge milestone, congrats!

PiotrSikora
PiotrSikora previously approved these changes Jan 22, 2021
Copy link
Contributor

@PiotrSikora PiotrSikora left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM sans nit.

against both untrusted downstream and upstream peers. As such our highest priority in risk assessment is the
threat posed by untrusted downstream client or untrusted upstream server traffic on the data plane. This
reflects the use of Envoy in an edge serving capacity and also the use of Envoy as a networking component in a
mesh deployment with unstrusted services.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: s/mesh/service mesh/

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

Signed-off-by: Yan Avlasov <yavlasov@google.com>
Copy link
Contributor

@PiotrSikora PiotrSikora left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@yanavlasov
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Signed-off-by: Yan Avlasov <yavlasov@google.com>
Signed-off-by: Yan Avlasov <yavlasov@google.com>
Signed-off-by: Yan Avlasov <yavlasov@google.com>
@yanavlasov yanavlasov merged commit 519ccfe into envoyproxy:main Jan 30, 2021
@yanavlasov yanavlasov deleted the threat-model-update branch February 1, 2021 19:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Harden Envoy against untrusted upstream servers

5 participants