Fri, 23 June 2017
Episode 198 – Building a Security Strategy – Part 1
Strategy is the hardest thing a CISO will do in their career...except if they have to explain a massive breach…
- What is a Strategy?
- What’s the difference between a strategy and a policy?
- A policy is binding statements
- A strategy is thought out planning
- A list of tech you want to buy
- A remediation plan that follows an audit/assessment
- A continued justification for the way you’ve always done things
- The stuff your favorite vendor told you needs doing
- What a strategy isn’t…
- Based on the needs and desires of the org and its senior leaders
- Culturally relevant
- A guide to where investment (money and people) need to be made
- Balanced between boldness and reassurance
- Built on a set of capabilities that map to business success criteria
- A strategy is…
- Creates a consistent frame of reference for talking about the program
- Helps senior leaders understand the where/why of the investments
- Lays out a connected story for CFOrg to make budget less hard
- Provides a decision-making framework that enables effective choices
- Why do you want one?
- Understand the business of your Business
- Know who your stakeholders really are
- Capability = (Tech + Service) * Process
- Crawl, Walk, Run
- It Takes A Village
- How do I make one?
In our next episodes we’ll break down each of the steps and talk more about strategy…
Direct download: SFS_Podcast_Ep_-_198.mp3
-- posted at: 8:53pm EDT
Wed, 7 June 2017
Episode 197 - After the Penetration Test
We've kind of talked about how to choose your vendors, and we’ll get more into services soon, but we wanted to take some time to talk about penetration tests and especially what to do as they wrap up, how they affect the organization, and how you can manage your penetration tests to make sure they're actually effective.
- Receiving the report
- First and foremost, you are the customer. The report is not done until you say it is done.
- That doesn't mean to massage the data, but you need to be sure that the penetration testers actually provided value.
- If there isn't a solid executive summary, send it back. Period. Your testers should be able to summarize what they did, what they found, and what they think for your executives.
- A Nessus or Burp scan is not a report. Ever.
- Always ask “how did we do for this application/organization size” etc. You’re not just paying for someone to run Nessus on your network, you’re paying for their analysis. Ask for that.
- Triaging the Results
- Results rarely go to the same place in the organization. You might have findings for different teams, or entirely different parts of your org. Make sure they get to the right people.
- Results may be inaccurate for your organization. A penetration tester isn't necessarily familiar with your organization’s risk profile, priorities, or anything else. What they mark as a medium may be a high or critical for you, or vice versa.
- Example: Information disclosure in Healthcare is often rated much higher when triaging than in other types of businesses.
- Working with the stakeholders
- Work in systems that make sense to people that need to do the work. Rally, Jira, etc.
- This can also give you traceability for when things are actually fixed.
- Don’t dump on people in big group meetings, take the findings to the specific teams
- That will give them time to develop a plan for the findings that are affecting them
- Managing upwards
- No matter how well or poorly the report is written, it’s still going to end up being your job to explain “how bad is this thing you handed me?”
- Have to manage the findings and their perception upwards
- Remediate, mitigate, or accept
- That's an upper management call
- Dealing with the Re-test
- Most penetration tests have a clause in there for re-testing findings. Make sure you actually take advantage of that.
- This looks good from both an actual security posture position and a management position
- Some penetration testers will let you remediate quickly and have them re-test, which can be reflected in the final report
- Especially if your report might going to customers, this is incredibly useful. Take advantage of this if at all possible.
Direct download: SFS_Podcast_Ep_-_197.mp3
-- posted at: 10:46pm EDT
Wed, 24 May 2017
SFS Podcast - Episode 196
Wannacry: Woulda, Coulda, Shoulda
First and foremost: Why was medical hit so hard by WannaCry? See Episode 189 - Medical Device Security and Risky Business 455 - https://risky.biz/RB455/
- The Lead-Up
- Threat Intelligence is A Thing
- Threat Intelligence is Hard
- Threat Intelligence Feeds are [REDACTED] for many/most
- Stay Calm
- You have finite human resources
- You have finite time
- Prioritize Your Responses
- Episode 192 - Security Waste
- Know what all your tools can do and be ready to use them
- Your Business Continuity Program can inform that
- You do have a BCP, right?
- Know what area to focus on first
- Be willing to cut off an arm to save the body
- When you can remember that Herd Immunity is a Thing.
- Scare the Children
- Waffle in decision making
- This is not the time to point out for the millionth time that your patching program is suboptimal
- This is not the time to point out that if you’d only gotten that BlinkyBox last capital season this wouldn’t be an issue
- Focus on what you can’t do
- When the Crisis Arrives
- Be sure you’re in Aftermath and not still in Crisis
- Do a Hot Wash and a full After Action Review/Post-Mortem
- Document your lessons learned and distribute them widely
- Follow Up, Follow Up, FOLLOW UP!!
- The Aftermath
Direct download: SFS_Podcast_Ep_-_196.mp3
-- posted at: 8:54pm EDT
Wed, 10 May 2017
Episode 195 - Annual Policy Review - Making It Worthwhile
- Define policy vs. standards vs. procedures
- What is a Policy? It is a guiding principle to set the direction of an organization. High level, governing, statements. Do not include technical details.
- Example: Policy statement = Users must authenticate with a unique ID and password
- Standard: User passwords must be: # of characters, include one uppercase letter, one special character, be at least 10 characters in length. This type of information would go into an Access Control Standard.
- What is a Standard? Standards support the policy, make it more meaningful and effective.
- What is a Procedure? A procedure is a step by step, how to guide to which is consistent with the end result being the same. These are the steps for configuring your firewalls, setting up a new user, building a server, etc.
- Every policy guide everywhere says you need to review your policies regularly which almost always means annually.
- Failure to do the annual review can get you in hot water with your regulator and/or auditor.
- It just Makes Sense.
- Why review your policies?
- It’s the one time a year you can nudge the organization where it needs to go
- Past Problems
- Current Issues
- Future Challenges
- Killing off/modifying policies that get in the way of people doing work will Make Friends And Influence People
- There is no better way to ensure your team is working on what needs to be worked on than aligning with stated policy.
- Making Sense of Policy Review
- Alert The Approvers
- Line Them Up
- Divide and Conquer
- Bring The Business Into The Process
- Internal Audit
- Corporate Security
- Marketing / Public Relations
- As Needed Bring In
- Change Crosswalks FTW
- Communicate, Communicate, Communicate.
- The Review Process
- Have a process to deal with questions. Route questions to the authoritative source for an answer - don’t answer stuff you can’t/shouldn’t
- Make sure what is being added is enforceable. This is a legal document and can be used in court. Statements support what is being done today, not what you would like to do or wish the program would do in the future.
- Go back to those “parking lot” statements that were not added or removed from a draft because you couldn’t enforce them at the time. Can they be added? Don’t lose sight of them if they are important to your security program
- Does the corporate culture / C levels support statements in the policy? As a security practitioner you may firmly believe that your security program must abide by certain policy statements but the corporate culture or your CEO/CFO even CISO may not support it. They may become “parking lot” items for a future version or you may be able to successfully display that the program can support that statement without affecting the culture.
- Legal is an important reviewer. It feels nitpicky during the review but Legal knows when “should” and “must” are appropriate.
- Don’t reinvent the wheel. ISO 27001 is a good framework for your policy. Use it. Don’t try to come up with statements because you think you have to appear to be an Info Sec Policy God. KISS!
- Don’t write standards and procedures in your policy! We’ve reviewed countless policies that had what we’d consider a standard or “step by step instructions for making firewall changes. That’s a procedure! Keep it out of your policy.
Direct download: SFS_Podcast_Ep_-_195.mp3
-- posted at: 8:21pm EDT
Wed, 26 April 2017
Evaluating Security Product Vendors
In light of recent news about “Vendors Behaving Badly” we want to talk about how a security professional should evaluate vendors and their products.
Tanium exposed hospital’s IT while using its network in sales demos: https://arstechnica.com/security/2017/04/security-vendor-uses-hospitals-network-for-unauthorized-sales-demos/
Lawyers, malware, and money: The antivirus market’s nasty fight over Cylance: https://arstechnica.com/information-technology/2017/04/the-mystery-of-the-malware-that-wasnt/
- There are so many different sources of information about vendors and their products. You owe it to yourself to evaluate not just the vendor but also each source of information.
- Analyst Firms: Gartner/Forrester/etc
- Always remember they take a very generic view using a notional enterprise as the standard.
- Current customer interviews are important but, remember, those customer contacts likely came from the vendor.
- The perception of “Pay for Play” is there no matter how much the firms want to squelch that.
- These tests presume a lot so make sure you understand what the conditions of the test were.
- The “Pay for Play” perception exists here too….
- The results of the testing aren’t specific but can help show outliers in a group
- 3rd Party Testing: NSS Labs, etc.
- Obviously your best and most relevant source of information. :-)
- If you have developed a reliable network of peers you can reach out and ask folks. But, remember, buy them a beer for their troubles…
- Always remember perspective is everything. Some people just don’t like Company_Z and will always hate their products.
- Information Sources
- Start with 3rd party data and demos. This will determine if your requirements (you did write out your requirements, right?) are met by the product
- Do not allow the vendor to drive the definition of “success” in a PoC
- Try to break it. I mean REALLY try to break it.
- Remember during the PoC is going to be the best support and interaction you will ever get. If that sucks you might want to move along.
- Test *all* of your use cases. (you do have documented use cases, right?)
- Do a PoC (Proof of Concept).
- Product Evaluation Rules
- Service providers such as penetration testers and MSSPs
- Edge Cases
Direct download: SFS_Podcast_Ep_-_194.mp3
-- posted at: 9:53pm EDT
Thu, 13 April 2017
Tonight's episode is all about those learning moments.
CISOs and security orgs find new and interesting way to screw up all the time. Leaving that Any-Any rule in place on the new firewall… Disabling the CEOs account by accident… Not realizing that Shadow IT had just installed a new egress point…
Here are our stories. The name have been changed to protect the culpable.
Direct download: SFS_Podcast_Ep_-_193.mp3
-- posted at: 10:02am EDT
Wed, 15 March 2017
Today's Topic: Security Waste - Buying new tools without maximizing use of current tool set
It’s not just a security problem but we often add to our arsenal without fully (or even mostly) utilizing the tools that we do have.
Problems associated with this are:
- Have more complexity in your environment
- Needing more staff or requiring current staff to stretch themselves thin to support differing tools
- Increased cost (capital, operational, support)
- Information overload - even with a SIEM more data requires more analysis
- Increased chance of missing key events
- Increased false positives
- What am I missing?
How do we work through this when you’re not the decision maker?
- “Operational Excellence” - Martin’s story
How do we work with our vendors to ensure that we are leveraging their tools without over dependence on one tool or vendor?
Direct download: SFS_Podcast_Ep_-_192.mp3
-- posted at: 9:02pm EDT
Wed, 1 March 2017
The Southern Fried Security Podcast - Episode 191 - Gone Phishin’
Phishing your employees - Does it make them aware or do they feel mistrusted?
- Intro - Phishing - what is it typically?
- Example - Emails from a Prince in Nigeria, phished on Match.com, etc
- What is it? An email designed to get employees to click on suspicious links or give their credentials
- Discuss what I designed as part of my phishing campaign - Partnered with trusted vendor
- Designed an email, google doc, supplied AD user list, launch
- Stats from our phishing campaign
- How GMail caught it and started dumping the emails into spam but some employees even went into spam and clicked (RSA breach!)
- Employees used Slack to warn others. Can you avoid neighbors leaning over the cube telling each other? Is this when “see something, say something?” becomes a good thing? How to get employees to follow it?
- What about when you phish your employees to improve security?
- How often?
- Do you target specific areas you know are susceptible (Ex - Marketing, Finance)
- What about Engineering? How do you trick them?
- What are the benefits of a targeted phishing campaign?
- Start with education first. Then to sanctions.
- Use to teach - not ridicule.
- C-Levels *have* to be part of it.
- How do you prevent employees from feeling that Security doesn’t trust them?
- People are still the weak link! Solutions and hardware can’t prevent that one user from clicking on a link that creates havoc for the company.
- We blow holes in security to allow Phish email through. What if vendor gets compromised?
Direct download: SFS_Podcast_-_Episode_191.mp3
-- posted at: 6:55pm EDT
Tue, 14 February 2017
Episode 190 - Burnout
- Why the topic of burnout?
- Because it affects all of us, and yet it’s not talked about much in this field
- Disclaimer: We am not a doctor. Or a psychiatrist or psychologist. Nor did we stay in a holiday inn express...
- Reason for sabbatical
- Martin’s story
- Personal Connection
- Symptoms may mirror depression
- “The Creeping Malaise”
- Panic Attacks, etc
- Isolation - even while in a crowd
- Physical symptoms
- It’s been around for a long time. http://www.secburnout.org/ & http://www.slideshare.net/secburnout/burnout-in-information-security are from 2011/12
- Recognizing Burnout
- “It won’t happen to me”
- “I just have to make it through this busy season and this end of quarter and the end of FY and…”
- “Everybody else is exactly the same…”
- Conferences are not vacations and shouldn’t be seen that way. Cons can be very hard work.
- Easy Traps
- Outdoor hobbies
- Just get outside and away from screens
- A physical, people you can talk to in person community
- Exercise & diet
- Creating and enforcing boundaries (emotional and physical)
- Mitigation Strategies
- Not liking your job or employer (that’s quite the opposite problem, actually)
- Just hard work for a little while
- What burnout isn’t…
Direct download: SFS_Podcast_-_Ep_190.mp3
-- posted at: 6:35pm EDT
Wed, 8 February 2017
In this inaugural bonus track we release the interview we did with Nick Selby (@nselby) on his experience validating the work of MedSec on St. Medical devices.
Direct download: SFS_Podcast_-_Episode_189_Bonus_Track.mp3
-- posted at: 7:55am EDT