Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Security Management

5/2/2019
06:00 AM
Marzena Fuller
Marzena Fuller
Marzena Fuller
50%
50%

Bootstrapping Security Programs: How to Gradually Implement an Enterprise-Level Security Program at a Fast-Growing Startup

You can't expect to build an adequate security program without investment in both people and security tools.

Given my experience with building and managing security programs at fast-growing, successful startups, I am often asked how to "bootstrap" security programs.

Investing in people and tools
You can't expect to build an adequate security program without investment in both people and security tools. The level of investment will vary based on a company's risk tolerance, customer verticals served and data processed. Ideally, a company should hire a senior technical security leader as part of their core team. Designing a product with security in mind, incorporating product security features aligned with go-to market strategy, making security a key element of development and testing processes and implementing security best practices early is a non-negotiable element of a solid security program.

However, that scenario is far from ideal for most startups.

Building a security program from the ground up

  1. Create a core security team. As I stated above you can't build an effective program without a dedicated security team. For a startup that means a senior security leader, an infrastructure security engineer, an application security engineer and a compliance professional. Each of these roles should be filled with an experienced professional who can develop a security roadmap, prioritize initiatives based on risk and implement processes and practices that will scale with a company's growth and can hire and develop their respective team. At the same time, the founding members of a security team must be hands-on and be able to execute on the critical elements of the roadmap themselves.

 

  • Create a partnership with engineering. A strong partnership with engineering teams is critical to building a successful security program. Firstly, engineers who work on the product can point out known product design security gaps and opportunities for improvement. Secondly, engineering time and commitment are required to implement a secure software development lifecycle, address pen test findings and implement customer-facing security features. This not an easy task especially at a startup where engineering has to execute on the product roadmap quickly while under resource constraints. However, it can be done successfully by demonstrating that addressing security early in the deployment pipeline will ultimately save time. This is a great example of how security can accomplish its objectives via influence rather than control.

 

 

  • Leverage automation. Leveraging security automation from infrastructure security monitoring and auto-remediation through static and dynamic code analysis and vulnerability management is essential. Implementing automation where possible will make security an inherent part of each process and ultimately allow engineers to save time.

 

 

  • Open source investments There are a number of very good open source security tools; however, it is important to remember that while they do not require a license fee these tools require time to implement and configure, which is not free. With a small security team in place investing in tools that can be implemented and configured by the vendor is often a more effective approach.

 

Implementing a successful security program from the ground up takes time and requires prioritizing initiatives based on risk and a company's risk appetite. A security roadmap should always be aligned with a company's go-to market strategy and expected growth.

— Marzena Fuller is the chief security officer at SignalFx.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/14/2020
Lock-Pickers Face an Uncertain Future Online
Seth Rosenblatt, Contributing Writer,  8/10/2020
Hacking It as a CISO: Advice for Security Leadership
Kelly Sheridan, Staff Editor, Dark Reading,  8/10/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
7 New Cybersecurity Vulnerabilities That Could Put Your Enterprise at Risk
In this Dark Reading Tech Digest, we look at the ways security researchers and ethical hackers find critical vulnerabilities and offer insights into how you can fix them before attackers can exploit them.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2015-8033
PUBLISHED: 2020-08-14
In Textpattern 4.5.7, the password-reset feature does not securely tether a hash to a user account.
CVE-2020-15692
PUBLISHED: 2020-08-14
In Nim 1.2.4, the standard library browsers mishandles the URL argument to browsers.openDefaultBrowser. This argument can be a local file path that will be opened in the default explorer. An attacker can pass one argument to the underlying open command to execute arbitrary registered system commands...
CVE-2020-15693
PUBLISHED: 2020-08-14
In Nim 1.2.4, the standard library httpClient is vulnerable to a CR-LF injection in the target URL. An injection is possible if the attacker controls any part of the URL provided in a call (such as httpClient.get or httpClient.post), the User-Agent header value, or custom HTTP header names or values...
CVE-2020-15694
PUBLISHED: 2020-08-14
In Nim 1.2.4, the standard library httpClient fails to properly validate the server response. For example, httpClient.get().contentLength() does not raise any error if a malicious server provides a negative Content-Length.
CVE-2015-8032
PUBLISHED: 2020-08-14
In Textpattern 4.5.7, an unprivileged author can change an article's markup setting.