Skip to content

Commit 70f68c4

Browse files
Update docs/Secure-Coding-Guide-for-Python/CWE-693/CWE-778/README.md
Co-authored-by: Bartlomiej Karas <[email protected]> Signed-off-by: andrew-costello <[email protected]>
1 parent 6e021b9 commit 70f68c4

File tree

1 file changed

+1
-1
lines changed
  • docs/Secure-Coding-Guide-for-Python/CWE-693/CWE-778

1 file changed

+1
-1
lines changed

docs/Secure-Coding-Guide-for-Python/CWE-693/CWE-778/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ Writing exceptions to stdout, stderr or local files is not sufficient as:
1212
* Trust level of stdout or stderr may be the end-user or attacker
1313
* Logfiles which are only on a local filesystem can be deleted by an attacker
1414

15-
If errors occur while recording logs, they can hinder the logging process unless preventive measures are implemented. Security risks can occur when these error's occur. For example, an attacker hiding crucial security issues by refraining the attacker from being logged. Therefore it is essential that logging functions in applications are effective, even when exceptions arise when completing the logging process.
15+
If errors occur while recording logs, they can hinder the logging process unless preventive measures are implemented. Security risks can occur when these errors occur. For example, an attacker hiding crucial security issues by refraining the attacker from being logged. Therefore it is essential that logging functions in applications are effective, even when exceptions arise when completing the logging process.
1616

1717
## Non-Compliant Code Example
1818

0 commit comments

Comments
 (0)