DEV Community

SimonR
SimonR

Posted on

Who Is Responsible for Security? Three Core Areas and Shared Accountability

Ask a plant manager who owns security and you may hear "IT." Ask the IT director and the answer might be "the plant." In many organizations, responsibility is spread so thinly that nobody feels fully accountable, which is when gaps appear.

This post looks at the broad areas security covers, who should own each, and how the answer changes in OT security in manufacturing, where physical safety is part of the equation.

The Three Major Areas of Security

If you search for the three major areas of security, you will encounter a few valid answers. One common grouping splits security into physical, technical (cyber), and administrative categories. Another uses people, process, and technology. Both lead to a similar message: protection is more than software.

  1. Physical Security

Fences, locks, badge readers, cameras, and secured control rooms. In a factory, physical access to a controller or engineering workstation can be just as dangerous as a remote attack.

  1. Technical or Cyber Security

Firewalls, network segmentation, endpoint protection, encryption, monitoring, and authentication. This is the area most people picture first.

  1. Administrative or Organizational Security

Policies, training, risk assessments, vendor contracts, audits, and incident response plans. These define how people behave and make decisions.

Strong programs address all three. A plant with excellent firewalls but unlocked cabinets is not truly protected.

So, Who Is Responsible?

The honest answer is that responsibility is layered. Here is one way to picture it.

Senior Leadership

Executives and the board set risk appetite, approve budgets, and ultimately carry accountability. They do not configure firewalls, but they decide whether security gets the resources and authority it needs.

The Security Function

A chief information security officer, security manager, or equivalent usually defines strategy, standards, and oversight. In industrial companies, this role increasingly includes explicit OT scope.

Plant and Operations Management

Site leaders understand production realities. They are responsible for ensuring that security measures are followed on the floor and that operational needs are communicated back to the security team.

Engineering and Maintenance Teams

These staff install, configure, and repair control systems. Their daily choices, such as how a vendor connects or how a password is stored, shape real security.

IT Teams

They manage enterprise networks, identity systems, and often shared infrastructure that touches the plant.

Employees and Contractors

Every person with access carries some responsibility: following procedures, reporting suspicious activity, and protecting credentials.

Vendors and Suppliers

Equipment makers and service providers must build secure products and support them properly. Contracts should spell out who handles vulnerabilities, updates, and incident cooperation.

The Gap Between IT and OT Ownership

Historically, IT owned networks and data, while engineering owned the plant. As the two merged, a gray zone appeared. Who patches an HMI that runs Windows? Who approves a firewall rule between the office and a production line? Who monitors alerts from an industrial network sensor?

Without clear answers, tasks fall through the cracks. A helpful remedy is a simple responsibility matrix that lists key activities and assigns an owner, a supporting party, and an escalation contact for each.

Models That Organizations Use

Centralized. One security team sets policy and manages tools across both IT and OT. This promotes consistency but may lack plant-level context.

Federated. Plants have their own security leads who follow central standards. This balances local knowledge with oversight.

Partnership. IT and OT teams work as peers with a joint governance group. This requires strong relationships but can be very effective.

No single model fits everyone. What matters is that responsibilities are explicit and leaders back them.

Accountability Versus Execution

A useful distinction is between who is accountable and who performs a task. Executives are accountable for outcomes. Engineers may execute the work. Confusing the two leads to frustration: leaders assume things are handled, and teams assume leaders will provide resources.

Writing down both roles for major areas such as patching, access reviews, backups, and incident response removes ambiguity.

Regulation and Legal Responsibility

In some sectors and regions, laws assign specific duties. Critical infrastructure operators, for example, may face reporting obligations and minimum security requirements. Directors can also bear responsibility for failing to exercise reasonable oversight. Organizations should consult qualified legal counsel for specifics, since requirements differ widely.

Practical Steps to Clarify Ownership
List critical security activities. Examples: asset inventory, access control, remote access approval, patching, monitoring, backup testing.
Assign an owner and a backup for each. Names, not just departments.
Define decision rights. Who can approve exceptions? Who can shut down a system in an emergency?
Document and communicate. A one-page summary on a shared site is better than a forgotten policy binder.
Review regularly. Reorganizations and new technology can quietly change who is responsible.
Culture Matters More Than Charts

Even the best matrix fails if people believe security is "someone else's job." Encourage a mindset where reporting a mistake is valued over hiding it. Recognize teams that spot issues early. Share short, plain-language stories of near misses so that lessons spread.

A Quick Example of Shared Ownership

Consider a request to open a remote connection so a machine builder can troubleshoot a packaging line. The plant manager decides whether the downtime risk justifies the request. The engineer identifies which controller needs to be reached. The security team confirms the access path is monitored and time-limited. IT provisions the account and removes it afterward. The vendor agrees to the conditions in writing.

No single person owns the whole outcome, yet each step has a clear owner. When any link is missing, such as nobody removing the account afterward, a small oversight becomes a lasting exposure. Mapping routine tasks like this one is a simple way to find where accountability is fuzzy.

In Summary

Security responsibility is shared across leadership, specialists, operations, suppliers, and every individual with access. The three major areas, physical, technical, and administrative, all need attention. The most resilient manufacturers make ownership visible, link it to authority, and revisit it as conditions change. For companies sorting through these questions, advisors such as Futurism Security can help structure the conversation.

Top comments (0)