Building A Security Operations Center SO
Building A Security Operations Center SO
(SOC)
2
Agenda
Introduction
Need for a Security Operations Center (SOC)
Components of an effective SOC
Deciding to insource or outsource the SOC
Outsourced SOC = MSSP
SOC requirements
Q/A
3
Building a Security
Operations Center
(SOC)
4
Current information security challenges
5
Why do you need a SOC?
7
Integrated SOC
IBM
8
SOC functions
Real-time monitoring / management
aggregate logs
aggregate data
coordinate response and remediation
Reporting
executives
auditors
security staff
Post-incident analysis
forensics
investigation
9
SOC planning
full audit of existing procedures, including
informal and ad-hoc
planning of location, resources, training
programs, etc.
plans change; don’t try to prepare everything
ahead of time
sometimes best approach is not clear until you have
actually started
build it like aircraft carrier - change built into design
10
SIM/ SIEM/ SEM tools
11
Challenge of SIM & automation
12
Which SOC?
Outsourced
Symantec, SecureWorks (Dell), Solutionary, WiPro,
Tata, CenturyLink (Savvis, Qwest), McAfee, Verizon
(Cybertrust / Ubizen), Orange, Integralis, Sprint, EDS,
AT&T, Unisys, VeriSign, BT Managed Security
Solutions (Counterpane), NetCom Systems and more
13
In-house SOC vs. outsourced MSSP
The Business Case for Managed Security Services Managed Security Services Providers vs. SIEM Product Solutions
http://www.solutionary.com/dms/solutionary/Files/whitepapers/MSSP_vs_SIEM.pdf
14
Define the SOC requirements
15
Internal SOC
Advantages Disadvantages
dedicated staff • larger up-front investment
knows environment better • higher pressure to show
than a third-party ROI quickly
solutions are generally • higher potential for
easier to customize collusion between analyst
potential to be most and attacker
efficient • less likely to recognize
most likely to notice large-scale, subtle patterns
correlations between that include multiple groups
internal groups • can be hard to find
logs stored locally competent SOC analysts
16
Internal SOC - Questions
17
Internal SOC success factors
1. Trained staff
2. good SOC management
3. adequate budget
4. good processes
5. integration into incident response
If your organization can’t commit to these five factors,
do not build an internal SOC – it will fail
will waste money and time and create false sense of security
if you need a SOC but can’t commit to these
factors, strongly consider outsourcing
18
Outsourced SOC
Advantages Disadvantages
avoid capital expenses – it’s their • contractors will never know your
hardware & software environment like internal employees
exposure to multiple customers in • sending jobs outside the
similar industry segment organization can lower morale
often cheaper than in‐house • lack of dedicated staff to a single
less potential for collusion between client
monitoring team and attacker • lack of capital retention
good security people are difficult to • risk of external data mishandling
find • log data not always archived
unbiased • log data stored off‐premises
potential to be very scalable & • lack of customization
flexible • MSSP standardize services to gain
expertise in monitoring and SIM economies of scale in providing
tools security services to myriad clients
SLA
19
Outsourced SOC – general questions
1. Can I see your operations manual?
2. what is its reputation?
3. who are its customers?
4. does it already service customers in my
industry?
5. does it service customers my size?
6. how long have its customers been with it?
7. what is its cancellation/non-renew rate?
8. how do they protect data and what is the level
of security at their SOC?
20
Outsourced SOC – staffing questions
1. what is the experience of its staff?
2. does it hire reformed hackers?
3. are background checks performed on all new
employees?
4. does it use contractors for any of its services?
5. are personnel held to strict confidentiality agreements?
6. what is the ratio of senior engineers to managed
clients?
7. what certifications are held by senior/junior staff?
8. what is its employee turnover rate?
21
Outsourced SOC – stability questions
1. Is it stable?
2. does it have a viable business plan?
3. how long has it been in business?
4. positive signs of growth from major clients?
5. consistent large account wins / growing revenue?
6. what is its client turnover rate?
7. what are its revenue numbers?
If private and unwilling to share this information, ask for
percentages rather than actual numbers
8. will it provide documentation on its internal security
policies and procedures?
22
Outsourced SOC - sizing / costs
23
Outsourced SOC – performance metrics
24
Outsourced SOC – SLA’s
25
Outsourced SOC - Transitioning
ensure adequate knowledge transfer
create formal service level performance metrics
establish a baseline for all negotiated service levels
measure from the baseline, track against it, adjusting
as necessary.
create internal CIRT
identify key events and plan the response
hold regular transition & performance reviews
be flexible
schedule formal review to adjust SLA’s after 6 months
of service operation and periodically thereafter
26
Outsourced SOC – Termination
27
Outsourcing: don’ t j ust trust - verify
Call Saturday night 2AM
Who’s answering? Do they sound competent?
Reports
Are they to your liking? Can they create complex
reports?
Set off a few alarms
Are they calling/alerting you in a timely manner?
True process for real-time threat analysis?
Or simply a glorified reporting portal that looks
impressive
28
Mike Rothman on MSSP
We have no illusions about the amount of effort required to
get a security management platform up and running, or what it
takes to keep one current and useful.
Many organizations have neither the time nor the resources to
implement technology to help automate some of these key
functions.
So they are trapped on the hamster wheel of pain, reacting
without sufficient visibility, but without time to invest in gaining
that much-needed visibility into threats without diving deep
into raw log files.
A suboptimal situation for sure, and one that usually triggers
discussions of managed services in the first place.
http://securosis.com/blog/managed-services-in-a-security-management-2.0-world November 2011
29
SOC analysts
30
SOC analyst – skill sets
• O/S proficiency • directories
• network protocols • routers/switches/firewall
• chain of custody issues • programming
• ethics • forensics
• corporate policy • databases
• services • IDS
• multiple hardware • investigative processes
platforms • applications
• attacks • and much more
31
SOC analyst - qualities
extremely curious
ability to find answers to difficult problems / situations
abstract thinker
can correlate IDS incidents and alerts in real-time
ethical
deals with low-level details while keeping big-
picture view of situation
can communicate to various groups that have
very different requirements
responds well to frustrating situations
32
SOC analyst burnout
33
SOC management
34
SOC processes and procedures
35
Sample SOC runbook table of contents
36
SOC metrics
37
Additional references
38
Apply
39
Apply
40
Ben Rothke, CISSP CISM
Manager – Information Security
Wyndham Worldwide
Corporation
41