Technology is advancing the capabilities of manufacturers across the board, but it is also boosting the number of malicious actors and their level of proficiency when it comes to cyberattacks.

That boost in technology from threat actors boosts the number of compromises of network devices and appliances.

Previous compromises affected physical and virtual network devices, such as edge perimeter security solutions and routers, as well as network attached storage. In the end, network devices and appliances are prime targets for malicious actors because they play a crucial role managing and processing traffic.

When targeting these devices, malicious actors have exploited vulnerabilities and insecure design features to gain and maintain valuable accesses. These actors can remain inside networks until detected and denied access.

These devices and appliances end up targeted when they lack secure by design/default aspects, regular firmware updates, or if they have weak authentication measures and provide limited logging, making it difficult to detect suspicious activity.

Schneider Bold
Increased Vulnerability to Attacks

Additionally, there may be improper configurations, lack proper network segmentation and use unsupported, or end-of-life (EOL) hardware, increasing their vulnerability to attacks.

Having said all that, there is a guidance available from UK National Cyber Security Centre (NCSC) in partnership with the Australian Signals Directorate (ASD), Cybersecurity and Infrastructure Security Agency (CISA), the Canadian Centre for Cyber Security – part of the Communications Security Establishment (CSE), theFederal Bureau of Investigation (FBI), and New Zealand’s National Cyber Security Centre (NCSC-NZ) that outlines expectations for the minimum requirement for forensic visibility.

The goal of the guidance is to help network defenders secure organizational networks before and after a compromise.

By following the minimum levels of observability and digital forensics baselines outlined in this guidance, device manufacturers and customers would be able to handle the detection and identification of malicious activity.

Device manufacturers should also use it to establish a baseline of standard features to include in the architecture of network devices and appliances, to facilitate forensic analysis for network defenders.

Best Practices
  • Devices and appliances should support the logging/recording of events related to:
  • Authentication including username, method used (such as password, SSH key, certificate, multi-factor authentication), source
  • IP address or hostname and relevant session identifiers for both successful and failed attempts
  • Technical support events and interactions that rely on tools from vendors requiring authentication using a specialized license key from the network device manufacturer
  • Service and application-level logging, such as HTTP/HTTPS requests and responses, interactive shell sessions (CLI) and similar services, including client IP addresses, request methods, URIs accessed, protocol versions, user agents, session identifiers, response status codes and the amount of data transferred
  • Process creation including parent process, executable path, username and arguments
  • Log the process exit code and termination reason (such as normal exit, crash, killed by signal)
  • Dynamic loading and unloading of modules and libraries, including the module or library name, version, file path, associated process ID and user context
  • File system creation, modification and deletion that could facilitate post- breach investigations, especially in critical directories such as the web root, configuration directories and system binaries
  • DNS queries performed including A, AAAA, TXT, SOA, NS, MX and PTR records, their responses, the querying process and the destination DNS server
  • Firmware or software updates, including successful and failed attempts, current and target version numbers, update source (such as URL or repository), digital signatures or checksums verified, user or process initiating the update and the full error messages encountered
  • Configuration backup, export and/or download operations
  • Log attempts to clear, rotate, or manipulate log files
  • Diagnostic, recovery and safety events
  • Peripheral insertions, such as USB, MMC, SDCard, etc

Click here for more information on the digital forensics and protective monitoring specifications guidance.

Pin It on Pinterest

Share This