“A Rose by Any Other Name…” – Selecting the Right InfoSec Professional August 22, 2012
Posted by Chris Mark in cybersecurity.Tags: CISA, CISSP, cybersecurity, data security, experts, information security, mark consulting group, qualfications, Social media
add a comment
Last week I had an experience that left me chuckling and shaking my head at the same time. I had been approached by a company that had some infosec needs. According to the person with whom I spoke, they had found me on LinkedIn and wanted to talk. This company had recently settled with some regulators over some privacy and other regulatory practices and were looking to beef up their security and compliance. I spoke to one person for about an hour and a half and was asked to send more info. Later that week I received a call from the person with whom I had spoken an was informed that the company was looking for someone with INFORMATION SECURITY experience. I (likely not so politely) asked what they thought I did for a living? His response was that the company was looking for someone with a computer science degree. It was curious that they did not say an information assurance degree, or cybersecurity degree…or…list an certifications or skills…simply computer science. Well then…there you have it. Apparently, this company feels the only real qualification for ‘infosec’ is a computer science degree. Considering their previous issues, you would think they would have a better handle on info sec and their needs.
When looking for an infosec professional understand that there are technical skills which are certainly important (encryption, configuring firewalls, devices, systems, app layer security etc., etc., etc.) There are other aspects which are important, as well. Understanding the compliance mandates as well as the various regulatory requirements and regimes is critical in today’s world. While not specifically defined as ‘infosec’, an understanding of privacy issues (how data is used) is also important. While understanding technology is critical, being a skilled infosec professional is about more than simply understanding technology and about more than computer science. While I may not have been right for that particular engagement for other reasons, the company’s laser focus on a ‘computer science’ degree at the exclusion of the other aspects suggests this company may be focused on the wrong areas. Maybe they should question why they had issues to begin with.
“You Can’t Unring That Bell!” – What is a”Data Breach” and When Should I Notify? August 21, 2012
Posted by Chris Mark in cybersecurity, Data Breach.Tags: cybercrime, cybersecurity, data breach, FISMA, HIPAA, HITECH, NPI, PCI DSS, PHI, PII, privacy, risk management, state breach notification
add a comment
There are currently over 45 state breach notification laws, several data protection laws, and numerous regulations including PCI DSS, HIPAA/HITECH, FISMA, and more. I frequently find myself working with companies on data breach notification plans. One of the more interesting (and heated) discussions comes when I ask them to define a “data breach” or “data compromise”. More interesting is when I ask them to define a “suspected data breach”. Visa’ rules state that “suspected” breaches must be reported within 24 hours of identification or there could be penalties. Consider the following example. You, as CSO, are informed of a malicious software outbreak in the customer service department. Does this require notification under the state breach notification laws, or relevant regulatory regimes? Maybe, maybe not. It is dependent upon a number of factors including access to data, data protections (ie. encryption), segmentation, the various laws etc. In short, it is not easy to decipher yet it is critical to be as accurate as possible.
Understanding what is, and what is NOT, a data breach or data compromise is the first step in defining your company’s data breach notification plan. The reason it is so critical is in the titled of this article. Once you notify that your company has been ‘breached’ you cannot ‘unring that bell’. The genie is out of the proverbial bottle and things start moving quickly. Most company’s would absolutely hate to make an announcement only to find that, while they may have experienced a security incident, it did not impact sensitive data (PII, CHD, NPI, PHI, etc.). It is important that you work with your compliance group, legal (don’t forget legal!), and the infosec & risk department to ensure you have a solid understanding of when, and under what conditions your company is required to notify of a breach or suspected breach. Here are some basic definitions to use as a starting point. (check with your legal council and don’t simply use these…there..that should protect me!;)
Security Incident/Event – Any event that compromises the availability, accessibility, or integrity of any asset. This includes systems, personnel, applications, services, etc.
Data Breach – Any exposure of or unauthorized access of sensitive and/or protected data to include PHI, PII, CHD, and NPI.
Suspected Data Breach– In the absence of direct evidence (identified fraud, or misuse of data, for example), any Security Incident in which it can be reasonable assumed that sensitive and/or protected data was exposed or accessed without authorization.
Remember, some state breach notification laws do not consider a breach of encrypted data as a trigger for notification…others do 😉 If you need help unraveling these issues (insert shameless marketing plug)…contact Mark Consulting Group…www.MarkConsultingGroup.com
graphic by Hippacartoons.com
“Bow-Chicka-Bow-Wow!” – Privacy Failure of Photobucket Can Make You a Porn Star! August 13, 2012
Posted by Chris Mark in cybersecurity, Data Breach.Tags: cybercrime, cybersecurity, data breach, fuscking, mark consulting group, Photobucket, privacy, security
add a comment
For those who like to use the popular photo sharing site Photobucket to share (ahem)..”private” pictures may want to take action immediately. According to an article on CNN, a privacy flaw in the way Photobucket allows users to share photos resulted in hackers gaining access to numerous R rated and even explicit photos of users. Photobucket allows users to share photos using direct links. This means that even if the user does not intend to share a photo, if a person can deduce the URL then the unencrypted file can be directly accessed. This is a hack known as “Fuscking” and it has been used to access numerous files. (more…)
“August 2012 TransactionWorld Magazine” – Chris & Heather Mark’s Articles August 13, 2012
Posted by Chris Mark in cybersecurity, Data Breach, Industry News.Tags: compliance, cybersecurity, data breach, data security, mark consulting group, mastercard, PCI DSS, security, visa
add a comment
Chris and Heather Mark both have articles in the August 2012 issue of TransactionWorld Magazine. Chris’ is titled: “The Impact of the Fortress Mentality & Today’s Compliance Strategies” while Heather’s is titled: “After the Compromise; Security Incident Response and Mitigating the Damage”
One note. I apparently forgot to update my bio with the Editor in Chief so the article erroneously references me as the Executive Vice President of Data Security and Compliance for a payment processor. You can visit Mark Consulting Group at the following: www.MarkConsultingGroup.com
“Tell me, Show me, Convince me”; Policies, Enforcement, and Auditing August 7, 2012
Posted by Chris Mark in cybersecurity, Risk & Risk Management.Tags: cybersecurity, information security, ISMS, ISO 27000, mark consulting group, PCI DSS, policies, risk, security
add a comment
I was speaking with a client yesterday about policies and auditing. He asked me a question and it reminded me of what I told my clients for years regarding policies. First, it is important to remember that a policy is NOT a document. The document is a record of the policy that was passed and tool for disseminating the policy. It should be a reflection of the policy that has been approved by management. Simply having a written document does not mean you have a policy. The policy must be approved, documented, disseminated, and enforced. Second, it is important to remember that writing and approving a policy is the easy part. Ensuring adherence with the policy and enforcing the policy is the difficult part. Make no mistake. A policy that is not enforced will not be followed for very long. People are inherently lazy (this writer included). We take the path of least resistance. Policies require difficult, often inefficient methods. Without enforcement, they will fall by the wayside. Third;writting, approving and documenting a policy is often much easier than implementing the policy. Consider the following example. Company X passes a policy that requires all computer and IT users’ access be modeled on “need to know” and “model of least privilege” (standard model). This alone requires an audit of every person’s existing privileges, as well as identification and documentation or their roles and responsibilities. Then each role would need to have access levels documented and assigned. As you can see, a simple one line policy statement may have deep implications. Finally, it is important to ensure that your company adheres to the documented policies. This is a three step process I describe as “tell me, show me, convince me”
1) Show the auditor that you have a documented policy that is updated, approved by management and disseminated to employees.
2) demonstrate to the auditor that you are currently in compliance with the policy.
3) convince the auditor that you have a history of following the policy by producing relevant documentation/evidence to show compliance over time. (last 3 months, last 6 months).
By using the tell me, show me, convince me model with policies and departments you can have confidence that your policies are being enforced, and followed.
