Has IT security gotten too restrictive, or is this just the job now?

November 17, 2026 5 answers
Asked by Virelka.9p

It feels like more IT work is taken up by patching, security requirements and rebuilding systems to meet changing policies. Is that a broader shift, or does it depend on how a company handles security?

Answers

v.263+plumshuttle

Some of the shift makes sense. A serious compromise can disrupt the business, and keeping up with vulnerabilities is a real maintenance burden. Security is not an optional extra just because a project would be more enjoyable without it.

That said, a security requirement should still have a reason behind it. Ask what risk a control addresses, what alternatives were considered, and who can approve an exception when it breaks something. That makes the discussion about tradeoffs instead of whether one team gets its way.

Vexdoro-7m:

Documenting the operational cost helps too. A control that takes months to work around has a cost that should be part of the decision.

Reply to this answer
4n~satincrank_627

This sounds at least partly like a governance problem. Security can identify risks and recommend controls, but the organization needs a clear process for deciding which risks to accept and who has that authority.

Bring a specific example rather than arguing that security has gone too far in general. Show the requirement, the incompatibility, the impact on the project, and a proposed alternative. If an exception is refused, ask for the reason and an escalation path.

Reply to this answer
Zori

I lean the other way. Running systems securely is part of the job, not an interruption to the fun stuff. Restricted service accounts, sensible permissions and encrypted connections should be normal design choices, including for tests and demos.

Building those in early can be less frustrating than bolting them on after a system is already in use. That does not mean every security rule is automatically a good one.

_h93!flindock.5:

Early involvement matters on both sides. Security needs to give the project team requirements in time to design around them.

Reply to this answer
5d!claspferrule_748

The amount of bureaucracy varies by workplace. Some teams have room to discuss exceptions and practical alternatives. Others may treat every security request as nonnegotiable, whether or not it fits the system.

If you cannot get a clear explanation or a route for raising problems, that tells you something about the organization. It does not necessarily tell you that all IT jobs work that way.

Reply to this answer
2e~coppergauge_735

There may also be outside pressure that the implementation team does not see. Insurance requirements and management's tolerance for risk can influence security decisions, though the actual obligations depend on the policy and organization.

It is reasonable to ask which requirements come from those decisions and which are internal preferences. The answer may affect how much flexibility there is.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions