Archistry

Survivability by Design™ since 2006

  • Home
  • About
    • Who Is Andrew?
    • C2T System™
    • The Agile Security System™
  • Contact
You are here: Home / Archistry Daily / Hell, no! I don’t care about your security policies!

September 30, 2019

Hell, no! I don’t care about your security policies!

Ever get the feeling that this is really what your business and IT customers are saying to you whenever you’re sitting in that last-minute security review and you catch them in violation of the security policies you know have been published for at least 6 months—and which they’ve had to go through (probably mind-numbing) mandatory training about?

Let’s put this in perspective a little bit.

Let’s say that I came up to you right now and said that you needed to walk backwards for the next 12 hours.

That’s it. No other reasons, no other guidelines.

No other…well….nothing.

Just do it.

“Why should I?” you might ask, somewhat belligerently.

And my terse reply would be, “Because I said so.”

Hmmmm….

In Transactional Analysis, a particularly interesting branch of psychology, the role I’m playing here is called “Critical Parent,” and the role you’re playing, assuming our scenario above, is called “Rebellious Child.”

And these are conditioned responses, often called “tapes,” that we learn early in our development and which influence every human interaction we have.

So…what’s this got to do with you and security, right?

Think about it for a minute.

The only way to break this sort of conditioned response is to use a 3rd role that we’ve actually able to control, influence and “rewrite” as long as we’re alive and making decisions. That role in Transactional Analysis is called the “Adult” role. And it’s only when we have Adult to Adult interactions we can have the ability to think critically, influence and have the greatest control of our decisions and reactions.

Our problem in security is that we tend to make some assumptions – often dangerous ones – that the business, or anyone not in security, is really just some petulant, “Rebellious Child” who doesn’t want to play by the rules and do what they’re told.

And when we do that, we’re channeling all the “Critical Parent” programming we’ve inherited from our childhood.

The reasons it’s called Transactional Analysis is that each human interaction is a series of transactions which fall into some common patterns. In the future, and, in particular, during my COSAC talk this week, I’m going to be talking about these more and how they relate to security and security architecture…

…but right now, what matters is that we can use this to our advantage and do what we can to break this pattern of interaction with our business customers.

Because if we can, it’s like tying a rocket to your butt in terms of building your credibility and trust with your customers.

Maybe that’s not important to you. And that’s perfectly ok.

But the point here is that if you’re not engaging the Adult of the people you’re trying to influence, they’re probably going to resent you telling them what to do—especially if you don’t have a boatload of credibility and trust with them individually.

So what do we do?

Well, we involve them in the process. We make sure that we understand their world, what’s important to them and don’t give them “silly restrictions” like my walking backwards example above that they don’t believe have anything to do with their world.

The good news: we don’t have to make this up.

It’s a formalized process called Requirements Engineering, or, as I mentioned the other day, we can call it Policy Engineering. And we can do that, because that’s really what it does for us.

It’s actually part of SABSA, and it’s built into the process, but if you want to understand how to avoid some of the common traps and pitfalls so you can be aware of what you’re really doing,

do it better than you might be doing it now,

and have the greatest chance of engaging your customers and getting their support for security,

then you’ll want to subscribe to the print Security Sanity™ newsletter before the 30th of the month. After that date, it’s going to the printer to be shipped to the 4 corners of the globe and into the hands of the eagerly-awaiting subscribers who will read it and learn something new they can immediately put to work.

Or not. It might not be your cup of tea. It’s expensive, after all, and there’s no guarantee it’ll work for you. So it might be a big risk. That’s why I want you to think carefully about it. It’s not for the impulse buyer.

It’s for the dedicated security professional who is passionate about constantly learning and becoming the best they can be in their careers and being as effective as they can possibly be in helping to enable and keep their organizations safe.

If this is you, here’s the link: https://securitysanity.com

Stay safe,

ast
—
Andrew S. Townley
Archistry Chief Executive

P.S. if you do happen to be at COSAC starting tomorrow, please make a point to say hello. Always great to put a face to a name and email, and I’m very interested to hear more about what you’re doing. Let’s grab a pint!

Article by Andrew Townley / Archistry Daily / Agile Security, Policy Engineering, Psychology, Requirements Engineering, SABSA, Security Policies, Transactional Analysis

  • Email
  • LinkedIn
  • Twitter
  • YouTube

EMAIL NEWSLETTER

Want to get DAILY email tips on how to build a more effective security program so you can prove your security investments deliver value to the business?

You can always unsubscribe at any time, and we won't sell your data to third parties.

About Us

Archistry works with you to ensure what you want to achieve actually gets done, linking strategy, risk, governance and compliance to enable sustained exceptional performance Read More…

Testimonials

Andrew is a highly skilled and experienced information systems architect and consultant, which in my view is a rare thing. He is innovative in his thinking and merits the title of 'thought leader' in his specialist domains of knowledge—in particular the management of risk. Andrew has embraced SABSA as a framework and, in doing so, has been a significant contributor to extending the SABSA body of knowledge."

— John Sherwood, Chief SABSA Architect

"Fabulous person to work with. Very engaging and insightful. Extremely good technical knowledge with ability to relate concepts together and overcome differing opinions. Makes things work."

— Kevin Howe-Patterson, Chief Architect, Nortel - Wireless Data Services

"Andrew was able to bring clarity and great depth of knowledge to the table. His breadth of thinking and understanding of the business and technical issues along with a clear and effective communication style were of great benefit in moving the process forward towards a successful conclusion."

— Doug Reynolds, Product Manager, MobileAware

"Andrew is a fabulous consultant and presenter that you simply enjoy listening to, as he manages to develop highly sophisticated subjects in very understandable way. His experience is actually surprising and his thoughts leave you without considerable arguments for any doubts in the subjects he covers."

— Biljana Cerin, Director, Information Security and Compliance

Recent Posts

  • If you want better security, you’d better have a better security architecture
  • The ultimate security song to keep you focused on what you’re doing
  • Security heroes
  • There’s always a people problem
  • Putting your data flow diagrams out to pasture…for good

Looking for something else?

  • Home
  • About
  • Contact

  • Terms of Service
  • Privacy Policy
  • Cookie Policy
  • Copyright © 2006-2025 Archistry Incorporated or its affiliates

"Archistry", the stained glass window logo, "Pragmantix" and the Pragmantix™ logo, "Archistry Execution Framework (AEF)", "Archistry Execution Framework, Cybersecurity Edition (ACS)", "The Agile Security System", "The Agile Business System", "Baseline Perspectives", "Architecture Wall", "Archistry Execution Engine", "Renegade Security", "Renegade Security System", "Security Value Delivery System (SVDS)" "Collapse-to-Traction", "Collapse-to-Traction System", "Adaptive Trust & Governance Model (ATGM)", and "Adaptive Trust & Governance Model for Organizations (ATGM4O)" are trademarks of Archistry Incorporated or its affiliates.