From 380201f2ac333ae7b87c96126f6ed1eea5622070 Mon Sep 17 00:00:00 2001 From: ff00ff-security <195214694+ff00ff-security@users.noreply.github.com> Date: Fri, 17 Jan 2025 13:05:20 +0000 Subject: [PATCH] Update Logging_Cheat_Sheet.md ampersand removal (#1593) Updating wording to remove informal ampersand. --- cheatsheets/Logging_Cheat_Sheet.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cheatsheets/Logging_Cheat_Sheet.md b/cheatsheets/Logging_Cheat_Sheet.md index 6fe9ec912d..03f76ec0fa 100644 --- a/cheatsheets/Logging_Cheat_Sheet.md +++ b/cheatsheets/Logging_Cheat_Sheet.md @@ -220,7 +220,7 @@ If your development framework supports suitable logging mechanisms, use or build Document the interface referencing the organisation-specific event classification and description syntax requirements. -If possible create this log handler as a standard module that can be thoroughly tested, deployed in multiple applications, and added to a list of approved & recommended modules. +If possible create this log handler as a standard module that can be thoroughly tested, deployed in multiple applications, and added to a list of approved and recommended modules. - Perform input validation on event data from other trust zones to ensure it is in the correct format (and consider alerting and not logging if there is an input validation failure) - Perform sanitization on all event data to prevent log injection attacks e.g. carriage return (CR), line feed (LF) and delimiter characters (and optionally to remove sensitive data)