Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

1.5.2 Verify that serialization is not used when communicating with untrusted clients. If this is not possible, ensure that adequate integrity controls (and possibly encryption if sensitive data is sent) are enforced to prevent deserialization attacks including object injection. #23

Open
kyrcha opened this issue Jul 7, 2020 · 0 comments
Open

1.5.2 Verify that serialization is not used when communicating with untrusted clients. If this is not possible, ensure that adequate integrity controls (and possibly encryption if sensitive data is sent) are enforced to prevent deserialization attacks including object injection. #23

kyrcha opened this issue Jul 7, 2020 · 0 comments
Labels
V1 Architecture, Design and Threat Modeling Requirements
Projects
Progress

Comments

@kyrcha
Copy link
Owner

kyrcha commented Jul 7, 2020

No description provided.

@kyrcha kyrcha added the V1 Architecture, Design and Threat Modeling Requirements label Jul 7, 2020
@kyrcha kyrcha added this to To do in Progress via automation Jul 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
V1 Architecture, Design and Threat Modeling Requirements
Projects
Progress
  
To do
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kyrcha