Skip to content

Commit 735f375

Browse files
authored
Update 0xa3-excessive-data-exposure.md
1 parent 20b011e commit 735f375

File tree

1 file changed

+6
-5
lines changed

1 file changed

+6
-5
lines changed

2019/en/src/0xa3-excessive-data-exposure.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -44,13 +44,14 @@ the site.
4444
data.
4545
* Backend engineers should always ask themselves "who is the
4646
consumer of the data?" before exposing a new API endpoint.
47-
* Use generic methods like "to_json" and "to_string" from the ORM / Model level
48-
very carefully.
49-
* Classify sensitive and personally identifiable information (PII) that your
50-
application stores and works.
47+
* Avoid using generic methods such as to_json() and to_string().
48+
Instead, cherry-pick specific properties you really want to return
49+
* Classify sensitive and personally identifiable information (PII) that
50+
your application stores and works with, reviewing all API calls returning such
51+
information to see if these responses pose a security issue.
5152
* Implement a schema-based response validation mechanism as an extra layer of
5253
security. As part of this mechanism define and enforce data returned by all API
53-
methods.
54+
methods, including errors.
5455

5556

5657
## References

0 commit comments

Comments
 (0)