Brand Your Security Program

One of the key challenges in building a security program is getting active participation from across the organization, from line workers to top management.  All of these people have “day jobs” and security is too easily put out of mind.

“Why Every Project Needs a Brand (and How to Create One)” appearing in the Summer issue of MIT Sloan Management Review has ideas to address these challenges.  Professors Karen Brown, Richard Ettenson and Nancy Hyer base the article on their research on project success and failure in a variety of industries.  I believe that security projects and security programs can benefit from their ideas, perhaps even more than projects with tangible business goals.  Opening a new factory has built in branding and awareness with clear and concrete goals and visible milestones along the way.  But security programs often operate in the background and branding must be more deliberate.

The five P’s of project branding, according to the authors are:  Pitch, Plan, Platform, Performance and Payoff.  These efforts go hand in hand with the actual project efforts, from start to finish.  The 5 P’s really focus on overall communication efforts between the security team and the rest of the organization.  The Pitch is the initial presentation to management, answering the question “why should we do this?”  For security it needs to address issues such as:  reducing risk, satisfying customer demands, meeting compliance requirements, improving efficiency.  The Plan is the time to bring in a broader group into the planning process.  This helps ensure that the security initiative will be successful and helps guarantee that participants will be on board after rollout.  The Platform is the vehicle by which the Plan is communicated within the organization or to effected third parties.  Performance includes communication of project results during the rollout phase.  Obviously it assumes success, but even that is not enough, if not appropriately communicated to the enterprise.  Finally, Payoff marks the completion of the initiative.  For example, this could be a celebration marking a successful audit result or the final implementation of an automated identity management system.  Without a clear “end point” in the project, participants may feel that their efforts have not been worthwhile.  This in turn, will effect their continued participation in this or other security efforts.

Branding is all about communication with stakeholders.  It importance in security programs results from the fact that everyone in the organization is a stakeholder in the organization’s security.

Frederick Scholl

Frederick Scholl is an accomplished Global Senior Information Security Risk Manager. Dr. Scholl earned a BS and Ph.D. in Electrical Engineering from Cornell University. In 1991, Fred founded Monarch Information Networks, LLC to enable forward-thinking organizations to protect their information. Previously, he co-founded Codenoll Technology Corporation (NASDAQ: CODN). He chaired the IEEE committee that wrote the first standard for Ethernet communication over fiber optic links, now used world-wide.

Book an Appointment for Cybersecurity Issues

Request an appointment with Dr. Fred Scholl. We will discuss any cybersecurity issues you have.

More Good Reading

Cybersecurity Thrives in An Organizational Context

The First National Cybersecurity Summit

New Privacy Laws Require Security Professionals Up Their Game

Cybersecurity Workforce Development: Real or Imagined Problem?

Antidote for Fake Everything

Information Security Risks, Gray Rhinos and Black Swans

Managing Information Security On a Limited Budget

Building a Security Start-Up

Cybersecurity Risk Management for Directors

My Reading List for Security Start-Ups

Should Your CIO Learn to Code?

How IT Leaders Can Keep a Seat at the Table

Equifax points out—again—the need for speed in security management

Anatomy of a Security Breach

The Smartest Information Security Companies

Book Review: Play Bigger

Long Term Beneficiaries of WannaCry

RISK: A NEW MOVIE ABOUT JULIAN ASSANGE

TRADE SECRET THEFT CONTINUES UNABATED

TENNESSEE LEGISLATORS MUDDY WATERS AROUND PRIVACY BREACH NOTIFICATION REQUIREMENTS

LEADERSHIP CHECKLIST FOR SECURITY PROFESSIONALS

SIEM VENDORS HAVE IT ALL BACKWARDS

THE SECRET TO GROWING YOUR SECURITY STARTUP

CLOUD JOBS PEAKING?

The Spy Who Couldn’t Spell

IS THERE A CYBERSECURITY PROFESSIONALS SHORTAGE?

No Blue Pill for Cybersecurity Failures

Presidential Cybersecurity Commission Makes Some Good Suggestions

Understanding Intelligence

Align Your Security Program With the Business

Don’t fall victim to BEC

Enterprise Risk Management and Information Security

Evidence Based Risk Assessment: Lessons Learned from the Y-12 Breach

First Conviction for Illegally Distributing Android Apps

Locking Up the Ivory Tower

Cloud Vulnerabilities

More Security Lessons Learned from the Y-12 Breach

Security or Compliance?

Home Disaster Recovery Planning

Cloud Computing: Trust but Verify

Background Checks May Not Be Enough

PERFECT SECURITY STORM FOR LAW FIRMS?

How Not To Be a Cyber Janitor

SECURITY MEMO: IT CAN’T HAPPEN HERE, CAN IT?

Don’t Forget Cloud Availability

Compliance v. Security

GAO Report on Information Security in Federal Government

Lean Security

Mitigate Your Social Engineering Vulnerabilities

HIPAA Security. Are We Making Progress?

Brand Your Security Program

PDCA is Dead

LEARNING FROM PAST MISTAKES

How Better Security Can Create Shared Value

C’est La Vie, You Never Can Tell: Lessons Learned from the HBGary Hack

DDOS Tutorial

The future of information technology

Data Governance Anyone?

Learning from the oil spill disaster

Down the Rabbit-Hole…Again?

Ideas on Risk Management