Intrusion detection systems (IDS) are tools that monitor network traffic and detect suspicious or malicious activity based on predefined rules or signatures. They are effective against known vulnerabilities, as they can alert the system administrators or security personnel when they encounter a match with a known attack pattern or behavior. However, IDS have some limitations and challenges, especially when applied to industrial automation and control systems (IACS). Some of these are:
* Modern IDS do not recognize IACS devices by default, as they are designed for general-purpose IT networks and protocols. Therefore, they may generate false positives or negatives when dealing with IACS-specific devices, protocols, or traffic patterns. To overcome this, IDS need to be customized or adapted to the IACS environment and context, which may require additional expertise and resources.
* They are not very inexpensive to design and deploy, as they require careful planning, configuration, testing, and maintenance. They also need to be integrated with other security tools and processes, such as firewalls, antivirus, patch management, incident response, etc. Moreover, they may introduce additional costs and risks, such as network performance degradation, data privacy issues, or legal liabilities.
* They are not effective against unknown or zero-day vulnerabilities, as they rely on predefined rules or signatures that may not cover all possible attack scenarios or techniques. Therefore, they may fail to detect novel or sophisticated attacks that exploit new or undiscovered vulnerabilities. To mitigate this, IDS need to be complemented with other security measures, such as anomaly detection, threat intelligence, or machine learning.
* They require a significant amount of care and feeding, as they need to be constantly updated, tuned, and monitored. They also generate a large amount of data and alerts, which may overwhelm the system administrators or security personnel. Therefore, they need to be supported by adequate tools and processes, such as data analysis, alert filtering, prioritization, correlation, or visualization.
References: ISA/IEC 62443-2-1:2010 - Establishing an industrial automation and control system security program, ISA/IEC 62443-3-3:2013 - System security requirements and security levels, ISA/IEC 62443 Cybersecurity Fundamentals Specialist Training Course, [Enhancing Modbus/TCP-Based Industrial Automation and Control Systems Security Using Intrusion Detection Systems]

Layer 2 of the OSI model is the data link layer, which is responsible for transferring data frames between nodes on a network segment. The data link layer is divided into two sublayers: logical link control (LLC) and media access control (MAC). The LLC sublayer deals with issues common to both dedicated and broadcast links, such as framing, flow control, and error control. The MAC sublayer deals with issues specific to broadcast links, such as how to access the shared medium and avoid collisions. The LLC and MAC sublayers are not related to the ISA/IEC 62443 cybersecurity standards, which focus on the security of industrial automation and control systems (IACS). References:https://www.baeldung.com/cs/data-link-sub-layers
https://bing.com/search?q=Layer+2+sublayers

Cybersecurity and physical security regulations are intended to provide guidance and requirements for protecting industrial control systems from various threats and risks. However, these regulations may face mixed resistance from different stakeholders for various reasons. One of the reasons is that there are a limited number of enforced cybersecurity and physical security regulations, especially at the international level. This means that some regions or countries may have more stringent or comprehensiveregulations than others, creating inconsistencies and challenges for cross-border cooperation and compliance. Moreover, some regulations may be outdated or not aligned with the current best practices and standards, such as ISA/IEC
62443, which may limit their effectiveness and applicability. Therefore, some organizations may prefer to follow voluntary standards or frameworks, such as ISA/IEC 62443, rather than mandatory regulations, as they may offer more flexibility and adaptability to the specific needs and contexts of each industrial control system. References:
* ISA/IEC 62443 Standards to Secure Your Industrial Control System, page 3
* Using the ISA/IEC 62443 Standard to Secure Your Control System, page 9

Phishing is a type of cyberattack that relies on a human weakness to succeed. Phishing is the practice of sending fraudulent emails or other messages that appear to come from a legitimate source, such as a bank, a government agency, or a trusted person, in order to trick the recipient into revealing sensitive information, such as passwords, credit card numbers, or personal details, or into clicking on malicious links or attachments that may install malware or ransomware on their devices. Phishing is a common and effective way of compromising the security of industrial automation and control systems (IACS), as it can bypass technical security measures by exploiting the human factor. Phishing can also be used to gain access to the IACS network, to conduct reconnaissance, to launch further attacks, or to cause damage or disruption to the IACS operations. The ISA/IEC 62443 series of standards recognize phishing as a potential threat vector for IACS and provide guidance and best practices on how to prevent, detect, and respond to phishing attacks. Some of the recommended countermeasures include:
* Educating and training the IACS staff on how to recognize and avoid phishing emails and messages, and how to report any suspicious or malicious activity.
* Implementing and enforcing policies and procedures for email and message security, such as using strong passwords, verifying the sender's identity, and not opening or clicking on unknown or unsolicited links or attachments.
* Applying technical security controls, such as antivirus software, firewalls, spam filters, encryption, and authentication, to protect the IACS devices and network from phishing attacks.
* Monitoring and auditing the IACS network and devices for any signs of phishing attacks, such as
* anomalous or unauthorized traffic, connections, or activities, and taking appropriate actions to contain and mitigate the impact of any incidents. References:
* ISA/IEC 62443-1-1:2009, Security for industrial automation and control systems - Part 1-1:
Terminology, concepts and models1
* ISA/IEC 62443-2-1:2009, Security for industrial automation and control systems - Part 2-1: Establishing an industrial automation and control systems security program2
* ISA/IEC 62443-2-4:2015, Security for industrial automation and control systems - Part 2-4: Security program requirements for IACS service providers3
* ISA/IEC 62443-3-3:2013, Security for industrial automation and control systems - Part 3-3: System security requirements and security levels4
* ISA/IEC 62443-4-2:2019, Security for industrial automation and control systems - Part 4-2: Technical security requirements for IACS components5

According to the ISA/IEC 62443 Cybersecurity Fundamentals Specialist resources, patches are software updates that fix bugs, vulnerabilities, or improve performance of a system. Patches are classified into three categories based on their urgency and impact: low, medium, and high. Low priority patches are those that have minimal or no impact on the system functionality or security, and can be applied at the next scheduled maintenance. Medium priority patches are those that have moderate impact on the system functionality or security, and should be applied within a reasonable time frame, such as three months. High priority patches are those that have significant or critical impact on the system functionality or security, and should be applied as soon as possible, preferably at the first unscheduled outage. Applying patches in a timely manner is a best practice for maintaining the security and reliability of an industrial automation and control system (IACS).
References:
* ISA/IEC 62443 Cybersecurity Fundamentals Specialist Study Guide, Section 4.3.2, Patch Management
* ISA/IEC 62443-2-1:2009, Security for industrial automation and control systems - Part 2-1: Establishing an industrial automation and control systems security program, Clause 5.3.2.2, Patch management
* ISA/IEC 62443-3-3:2013, Security for industrial automation and control systems - Part 3-3: System security requirements and security levels, Clause 4.3.3.6.2, Patch management