SANS MGT512 Day 2

As I mentioned in the last post, Day 2 gets pretty technical. However, for this class, the importance is to understand the concepts so that, as a manager, you can make educated decisions around technical concepts. You don’t have to know the math for Elliptic Curve Cryptography, nor do you have to memorize the seven layers of the OSI stack. You should be able to understand when someone says, ” This is a layer 7 firewall.” though.

Day 2 is titled Protecting Data and Networks so, unsurprisingly, that’s the focus of the day. This day, similar to day 1, lays a foundation for security that covers the concepts and tools that we need to secure our data as well as the network infrastructure. The network portion also gives us the basic knowledge we need as managers to be able to understand why we would want to encrypt something at layer 3 vs. layer 7.

The day is pretty much split in half, with the focus of the first half being on encryption and privacy, and the second half being on networking. Encryption looks at:

  • Encryption Concepts (things like symmetric vs. asymmetric encryption)
  • Encryption algorithms; enough to have an understanding of how they work, but without having to do really hard math.
  • Encryption applications; things like VPNs and Email encryption
  • There’s also a short unit on privacy where we discuss the overlap of privacy and security and what some of the key privacy concepts are (PII, Consent, and some legal precedents)

The network section is a bit of a deeper dive as it’s good for managers of technical staff to have a slightly deeper knowledge base. With this knowledge you will have to ask fewer questions and you’ll be better prepared to discuss products with vendors and concepts with non-IT management. The sections are broken up in layers (TCP/IP stack layers, not OSI stack layers) and are as follows:

  • Layers 1 and 2 overview and attacks
  • Layer 3; more discussion on VPNs and encryption at this layer, as well as an introduction to IP version 6.
  • Layer 4 with discussion of both TCP and UDP.
  • Application layer discussing proxies, firewalls, and other technologies that apply to network layer security

Day 2 is a heavy day and your head will be very full by the end of it. However, I’m pretty confident that you’ll find it is either an excellent refresher for those who once knew this stuff really well, or a solid, practical, introduction for those who may have come from non-technical areas of the business. In either case, it does a great job of preparing you for the topics around system security that come on day 3.

SANS MGT512 Day 1

If you’re not familiar with it, this class is very true to it’s full name: Security Leadership Essentials. It’s designed primarily for two types of audience; 1) Non-technical managers who have to manage technical security people and, 2) technical people who are now managers but haven’t had much formal management training. It works for a lot of other types of security professional too, but those are for whom it is really perfect.

This duality of audience means that the class has a bit of a duality itself. You’ll learn about the essential security concepts that security managers need, and you’ll get an introduction to management with a focus on managing a security program. For the management “half” the focus is, now more than in previous iterations, on managing a security program and interfacing with the business. We all know that security managers today need to understand and communicate in terms the business understands and this class helps with that. The technical “half” is designed to help you understand the key concepts that the teams you’ll manage deal with on a day-to-day basis. This helps to ensure that you and your team are communicating effectively, just as you must with management.

So what does day 1 bring? Day 1 is all about building a program; We understand that today, security isn’t just about buying fancy toys, but it also includes communicating risk to the business and measuring how well you are identifying and mitigating those risks. This day is, like day 1 in most SANS classes, all about building the foundation for what is to come the rest of the week. The security program is the fundamental piece for the week. Topics include:

  • Security Frameworks. Specifically control, risk, and program frameworks including introductions to the CIS 20 Critical Security Controls, NIST Cybersecurity Framework, and the FAIR model for quantitative risk measurement.
  • Understanding Risk. How do we define, communicate, and measure it?
  • Security Policy. While not everyone’s favorite, nor most thrilling topic, it is one that is crucial to the foundation of an effective security program. This section includes material from SANS MGT514 – Strategic Planning, Policy, and Leadership, also written by Frank Kim.
  • The day ends with material focused on the Who, What, Why, and How or, the Program Structure. It delves into what all of the pieces of the program are and how you put people and process together into a workable format. This helps to ensure you have all of the necessary duties covered and an organizational structure that fits your company.

Along with those topics, there are some group discussions to alleviate what can seem like an endless number of slides. These discussions help you to better understand the frameworks you use, how you can quantify risk, and where you might have gaps in your policies. Day 2 gets technical pretty fast, so get ready.

SANS Security Leadership Essentials – MGT512

I’ve taught this class for a number of years now and it has always been one of my favourites. It was usurped for a time by “Implementing and Auditing the CIS 20 Critical Controls” (SEC566) as 512 became a bit dated and I found 566 to be a bit more relevant. However, that all changed this year when a significant re-write was completed and the new version of the course went live. Frank Kim and other contributors have done a great job of bringing this back to be a true essentials course.

I’ve taught a couple of classes already and have a bunch more lined up this year so I thought I’d take some time to give a run-down of the new material and let you know what to expect. This class has quickly risen in the popularity ranks once again and it’s a great opportunity for people in a variety of roles to get a thorough introduction to security and management principles. Stay tuned for the next 5 posts to learn more about this great class.

Day 1
Day 2
Day 3
Day 4
Day 5

Join me for this class, next in New Orleans, Louisiana

The times, they are a changin’

It’s World Password Day and there seem to be a lot of posts suggesting that the end is nigh for passwords. I’m here to burst that bubble; Passwords may be going away, but not anytime soon, and so we still need to make sure that we’re taking care of all of the ones we have.

Passwords are still around because the user experience is really good. We know that to get into our favorite apps and websites, we need a username and a password. We memorize the passwords so that we really don’t have to do anything other than type it in to the box. We don’t need to go searching for a USB thingy to plug into our computer, we don’t need to go and get a code from some other device, we don’t need to find that book that we write them all down in. Username, same old password, done. The problem is, we’re not machines and we don’t have computers for brains. Therefore we take short-cuts; We use simple passwords and instead of choosing one for each site, we re-use the same simple passwords over and over again. This makes the experience even simpler but leaves us open to major breaches of our privacy and information.

Companies don’t help. Make sure the password is at least 8 characters, has at least one capital letter, one lower-case letter, one number, and one special character. You have to change it every two months and you can’t re-use the last 10 passwords you used. Oh yeah, don’t use your name, your pet’s name, your favorite sports team’s name, any variation on the company name, your mother’s maiden name, and no repeating characters. Passwords are hard and we’re really good at making the whole process harder.

There is a better way though and it isn’t the disappearance of the password (although that would be great). Times are changing because of the understanding that length is the most important characteristic of passwords, not complexity. Your password needs to be long, but memorable, and you should use a unique one for each service that requires one. Humans are good at remembering long, but simple things. It’s all that complexity stuff that tries our brains.

How hard is this to remember? “apple\Spiders2puppies” Not hard, and that’s a 21 character complex password (Pro Tip: Don’t use that example as your password). Variations of this for each different site or app are just as secure, but different.

Still don’t want to have to remember all of those passwords? Sign up for a password vault service like LastPass, 1 Password, DashLane, or a free local password saver like KeePass. The advantage to these tools is that they are integrated into your browsers and automatically fill in your passwords in addition to allowing you to generate completely random passwords. I only know the password to my manager, I have no idea what my passwords are for the vast majority of sites and apps I use. Of course, you should also use 2 factor authentication, also referred to as two-step verification. That’s another post on its own though.

So in honour of World Password day, go sign-up for a password manager and change all of your passwords. If not a service, at least change all of your passwords using the premise that length is most important. You’ll be glad you did and your online life will be easier and more secure. How often do we get to say that?

Crowdsourcing: I need your help.

I’m looking to build a presentation for a future conference and I need your help. My subject is “Communicating with Managers” and is intended to help non-management security folks better communicate with non-security security managers. Seem clear?

Here’s what I need from you: I’m looking for your stories, tips, or rants for when you’ve a) had to communicate with a security manager who wasn’t a security person or b) you’re a manager who has seen far too many technical people fail to communicate their message to you.

You can leave your story as a comment or tweet it to me @kentonsmith and I’ll be sure to share the presentation once it’s polished and ready to go.

End-to-End WhatsApp: An Opinionated Series on Why Signal Protocol is Well-Designed

Here’s a good look at what the Signal protocol is all about.

“WhatsApp recently announced that client communications are now end-to-end encrypted using Open Whisper System’s “Signal Protocol” (previously Axolotl). This has received quite a bit of press lately due to WhatsApp’s massive user base, along with the controversial going dark debates. Less importantly, the crypto-nerd in me loves Signal. Because of all of this, I thought I would write a blog series on some of Signal’s design decisions that I feel are well-designed.”

Source: End-to-End WhatsApp: An Opinionated Series on Why Signal Protocol is Well-Designed

It’s About Privacy Not Morality

ashley_madison

When it was announced, back in July, that the Ashley Madison site was hacked, like many, I thought about the fact that a bunch of people would be getting their just desserts. However, when the data was leaked (and continues to be leaked) a couple of days ago I started to think more about privacy than karma. All the jokes about those affected by the Ashley Madison breach are distracting us from the fact that people’s lives are being negatively affected by a criminal act over which they had no control. People who had an expectation of privacy, Ashley Madison bragged about it a lot, lost that because someone else decided that a cheating spouse deserves less privacy than someone else. Today it’s a site that caters to people who have different morals from many of us (or none at all depending on your point of view), tomorrow it could be the site you’re using to find a new job while still working the one you have.

Data breaches are happening so often these days that people are trying to group them into which ones are more serious than others. Is stealing nude photos from a celebrity’s phone worse than stealing credit cards from an adult website? If you shop at Target are you more deserving of having your credit card information stolen than if you shop at Neiman Marcus? Most people would scoff at those comparisons and say; “They’re all bad.”. So why do we think that people who signed up for Ashley Madison, whether they used it or not, are more deserving of losing their privacy than those who’ve signed up for Match.com?

We’re losing our privacy, or ability to have any, at an alarming rate these days. Tying privacy to morality, socio-economic level, social status, or anything else means that someone will always consider us undeserving of it. Everyone needs privacy and no one but the person requesting that privacy should get to decide whether they “deserve” it or not.