Skip to main content

Security Software and the Cowboy pants

Starting to feel a sense of frustration. No it doesn't effect me personally. I am still the same 'white hat' as always.
I went through the series of interviews for different positions recently. It was an absolute waste of time. What caught my attention is a level of arrogance and mindless stupidity coming from the people who should be paying attention. Each interview was along same well travelled paths:
Can you install software?
Can you connect it to the ERP (or whatever they connecting it to) ?
etc.
So they all concentrate on the Functional requirements. Most forget the security of your software falls into the Non-Functional requirements.
No one had a slightest idea that before you implement Functional requirements you need to make sure that your 'Security Software' being it Sailpoint, Oracle or Forgerock or whatever:
is in itself secured.
The buzz word 'security software' doesn't make it to be secure on its own.
Someone has to do it.
Otherwise your Security Software will be looking like a cowboy wearing pants with two guns in the front pockets and two wide cutaways in the back.



Yes your company rear will be exposed.
Almost all of the vendors use 3 tiered system:
Front web tier
Application tier
Database Tier
If none of these tiers are hardened and secured you will end up with the pants above.
Any IAM implementation project therefore need to start and concentrate on fulfilling the Non-Functional requirements first and foremost.
Only after the Non-Functional requirements are tested and approved the Functional requirements can be addressed.
I strongly recommend to follow NIST, ASD and some other standards to secure the 'Security Software'.

But you can always buy pants as they are widely available out there :) and plenty of integrators who are happy to sell them.

Comments

Popular posts from this blog

Mediator vs OSB

Many times in my classes and projects people mix between Mediator and OSB Now picture above tells a story :) Mediator only works within Composite App OSB enterprise wide integrations, SLA's etc. Mediator and OSB do have overlapping functionality and the final differentiation: 1. OSB only used for non-functional requirements and its job is to Virtualize and route. 2. BPEL on the hand used for Orchestration between different services. Last picture will tell a better story :)

Locomotive Breath

Living through the transition period is quite extradionary. We all kinda know and anticipate the outcome but not in a position to do anything about it. Like watching your train leaving the station and taking you for a ride. Matrix showed us the final result with humans being used to power machines. We all in one or the other way using our own energies to breathe the life in cold metal - building networks, programming and maintaining computers. They getting smarter and smarter and we are all excited about the possibilities of artificial intelligence. But the train will arrive to the next station and it will be our turn to get off. The train will be smart enough to move on its own without us. The train will be smart enough to look for sources of alternative energy if we try to stop it. Jethro Tull - Locomotive Breath https://www.youtube.com/watch?v=i19d1QnstsA&list=PLvy5jih231dYToxVkCz4xN2SX6zqVkeYT&index=17

Bees and Honey

"Another challenge is that identity data is typically decentralized . The Department of Motor Vehicles issues drivers licenses, for example, while the Department of Homeland Security issues passports, banks track financial histories, and so on. Most of these organizations have isolated and centralized identity management systems, but the current landscape demands federation and single sign-on (SSO). This makes identity management, protection and verification very cumbersome, costly and risky for all industry enterprises and government agencies." Jai Singh Arun - Security and Blockchain Innovations Program Director, IBM Identity architectural landscape is changing and personally I can only think of this very simple analogy between identities and blockchain. Identities to the blockchain are what the bees are to the honey. . This is as simple as even your grandma would understand :) Bees (identities) all day collect honey somewhere in the fields. Coming back to thei...