If you have a business, you have to be careful about your business secrets.
That’s how it is for the IT world. In fact, many companies have a number of people who are not trusted in some way, whether they are the company CEO or the manager of one of the company’s departments. One of the reasons they have this situation is because they don’t trust the people who have access to sensitive company information.
There is a difference between trusting someone and having access to their secrets. A very public trust relationship is one in which a person has access to a business’s secrets. It’s not the case with most of us, especially in the information-technology world. A private trust relationship is one in which a person has access to a business’s secrets, but they have no reason to believe that they are the one who is privy to those secrets.
We’ve all had a friend who was a security guard for a tech company. They were just a regular guy, but they had a great job and they got the job of doing security for that company. They had no reason to believe that they were the person who was actually privy to that information. One day, when they had no longer been a good friend, they confided in us that they had done something very, very wrong.
The reason we know they were so wrong is that their company’s security system was breached by a hacker. So they were able to access all sorts of sensitive employee data and pass it to someone they did not know. They were able to use a secure channel to do this and they were not even aware that it was happening. We don’t know who the hacker was, but it might have been a friend of theirs, one of their own, who they had told about what had happened.
When this happens, we call our security company and they call us. Then we call our customer service. Then we call their security department. Then we call the hacker. Then we call the customer service and explain what happened. Then we call the hacker. We end up with a series of different people and security procedures to figure out what happened.
We call our customer service, because they did our security department a favor by catching the hacker and they were the ones who told us about what happened. When you’re dealing with a third party that you know is a security threat, you need to establish a relationship, so you call them. They then call your security department. They then call your customer service. Then they call the hacker. Then you call your customer service, and explain the problem.
It turns out that the hacker had been contacting the customer service department for some time, but could not establish a connection with it. He then called the customer service. Then he called security. Then he called the hacker. Then he finally called security again, and explained the problem. He then asked the security department if they knew anything about the hacker and they said they did not.
That’s why you can’t just say “we don’t know about your problem.” That is a lie. They are not going to be open to that because they have an obligation to protect your customers. Even when they are not getting anything from you, you are still getting all the information you need from them and they have an obligation to use that information to help you.
In other words, you cant just assume that the security department will be open to your problem unless you have proof that they are actually going to give you what you need. If they are not going to give you any information, then you have no proof that they will help you. I think it goes both ways. If you dont know anything about the hacker and he keeps asking for information about your issues, then you do not have proof that he is going to help you.
