We have one job at Critical Assets. That is to furnish our
clients with a report detailing the deliverables that we’ve promised them, and
to do that on time. Everything leads to that - it’s what they are paying for.
As a sales guy, I sit through endless meetings, and hours of
discussion while getting to know our clients. One thing I can say for sure is that
our client list is as diverse as the weather in tornado alley during the summer,
but all of those clients have one thing in common: They want to know about the
security of their network perimeter, how holey their web apps are, or how
effective their product is at stopping attacks. When we give them their
deliverables they can do what they really need to, which is remediate the noted
deficiencies, or chose to accept the risk.
Not knowing is always the most difficult part, and waiting for answers to something as paramount as security can drive people insane. I like sane customers, and I don’t need engineers driving them insane. If you do, I will barbeque you. For those of you who’ve met me, you know I’m a man who can consume substantial quantities, so I have no problem trying for an engineer-sized burger.
When customers wait for deliverables, this means they also have to wait to start remediation. Waiting for remediation means increased exposure to a security breach and re-testing delays. Every salesman and every engineer knows that clients make you hurry up and wait for a variety of reasons – and we’re quite accustomed to this. It is however, an unacceptable practice in return.
Not convinced? Try me. I’m ordering this right now on ebay:
No comments:
Post a Comment