Welcome!

Microservices Expo Authors: Pat Romanski, VictorOps Blog, Derek Weeks, Jason Bloomberg, AppDynamics Blog

Related Topics: Cloud Security, Microservices Expo, @CloudExpo

Cloud Security: Article

Information Security from a Business Perspective

It must be designed and implemented as a core ingredient of the business strategy

As enterprises struggle to remain profitable in an ever-changing risk environment, the current economic crisis has elevated the need for effective business risk management. Information security is a key parameter that affects business risk. The academic definition of information security is the "preservation of confidentiality, integrity and availability of information." [1] Confidentiality is the preservation of secrecy of information (e.g., business reports, technical designs or financial projections) by ensuring that viewing is conducted solely by authorized people. Integrity is ensuring that information is accurate and consistent and has not been manipulated. Availability ensures that information is accessible to authorized people when needed.

Historically, information security has been addressed primarily as a technical issue. Preventive controls, such as firewalls, user access control mechanisms, encryption of data and communications, digital signatures, data backup systems, and detective controls, such as intrusion detection systems or security monitoring platforms, have formed the basic components of security architecture. Often, the technical controls are complemented by a set of security policies, procedures and guidelines aimed at controlling the actions of personnel.

This approach, though, has proven to be insufficient. Security incidents continue to rise and security problems remain unsolved while information security experts have been challenged to effectively communicate the value of information security to enterprise management. The root cause of these problems may be the definition of information security itself. There is a lack of consistency as each sector, industry and even enterprise has had to define information security uniquely, based on very specific business needs. This lack of consistency has contributed to a lack of understanding and a lack of appreciation for the value of information security.

Information Security Defined
To define information security in an organisation, one must understand its business objectives, identify stakeholders and link them to information protection attributes. Organisations have to be trusted to achieve customer acquisition and retention, which directly affect their revenue. This trust is a key success factor that is directly related to:

  • Business integrity-Each business decision is conducted as described in its official literature. It is fair to the customer and inspires trust. Information integrity (avoiding data manipulation) is a key information security component related to customer trust.
  • Customer asset protection-Customers need to be confident that their money, credit card numbers and bank account numbers are safe, especially in online transactions, where their funds are essentially electronic. Customers need to trust an organisation to secure their financial assets; confidentiality, integrity and availability are crucial security parameters.
  • Customer privacy-Customers provide their personally identifiable information (PII) to a whole host of ‘trusted' sources. As in customer asset protection, trust in the business is important for making them feel comfortable with sharing such information. Trust is particularly important when dealing with large amounts of money because customers have to feel safe and also that their personal data have been protected.

Providing services to the public also has societal and political facets. Businesses must adhere to a governmental regulatory and legal framework. The provision of secure and fair outlets to citizens is a matter of social responsibility. Moreover, the government is a shareholder of business (directly or indirectly through taxing); thus, business success affects the corresponding governmental revenue.

The aforementioned facts are clarified in relation to information security when the drivers of shareholders' trust are studied in more detail. For example:

  • Each licensed business has to comply with rules and terms of the license, which in turn have general or more detailed information protection requirements. These vary from general statements for fairness, antifraud rules and service availability requirements to more detailed technical controls such as network security rules, operating security policies or certification requirements. Shareholders need to be confident that a business complies with the license obligations and, more generally, the legal and regulatory framework, since this is a main corporate viability factor.
  • In competitive business environments, information security acts as a competitive advantage that, in turn, ensures customer acquisition. Shareholders trust a business if it operates as a competitive corporation, and due to the importance of protecting its information from breaches, information security becomes a competitive parameter.

In relation to the business role of information security, drivers should be:

-Shareholders' trust:

. Corporate viability, which is driven by compliance of license terms

. Competitive advantage, which ensures customer acquisition

. Brand name value preservation, which ensures customer retention

. Legal and regulatory compliance (e.g., the integrity of financial records and PII protection)

- Customers' trust:

. Business integrity

. Service availability

. Protection of the confidentiality of customers' sensitive information

Using this definition of information security for the business sector, a holistic approach is required for addressing the information security requirements of each unique organisation. This requires a detailed business analysis for embedding information security into the specific business processes and also for addressing the human factor and minimizing the uncertainty it introduces.  International security standards provide a solid base for information security from a business perspective.

THE INFORMATION SECURITY STANDARDS LANDSCAPE
In 2006, the Security and Risk Management Committee of the World Lottery Association (WLA)2 published the most recent version of its Security Control Standard (SCS). This standard describes a number of information security controls (technical and procedural) tailored to the lottery sector. Indicatively, it includes rules regarding the management of lottery draws and protection of prize money and Internet gaming systems.

The Security Control Standard (SCS) is an extension of the globally recognized information security standard ISO 27001 of the International Organization for Standardization (ISO), which is related to the establishment of information security management systems (ISMSs). Such systems provide the framework for managing information security from planning to implementation, monitoring and improvement.

ISACA has published a set of information technology (IT) auditing standards and the Risk IT:  Based on COBIT framework, which provides a set of guiding principles for effective management of IT risk. Risk IT complements COBIT, a comprehensive framework developed by ISACA for the governance and control of business-driven, IT-based solutions and services. In 2009, ISACA published An Introduction to the Business Model for Information Security, the first publication  released under the Business Model for Information Security (BMIS), which addresses information security from a business perspective, and in 2010, the full model was published as The Business Model for Information Security.

Other standards include the Payment Card Industry Data Security Standard (PCI DSS), a set of requirements for enhancing payment account data security, and the Special Publications (800 series) of the US National Institute of Standards and Technology (NIST), which are documents of general interest to the computer security community. The aforementioned standards provide an indicative view of the information security standards landscape. Other standardization bodies and associations provide their own guidelines in the field. In addition, technical security best practices of system vendors provide additional guidelines.

The modern business sector has to select the information security standards to use as a basis for its security architecture, and it must customize this selection according to its specific business needs.

 

Case Example from the World Lottery Association
In this particular example the ‘customer', so defined by the business model, is identified as the ‘player'. In this situation the definition of information security, specific to the lottery model, also becomes altered. ‘Business integrity' becomes ‘game integrity', ‘customer asset protection' becomes ‘player asset protection', and ‘customer privacy' is therefore ‘player privacy'. In terms of security the needs of a customer and player are much the same; however, due to the proactive nature of a ‘player', whose object is to win prizes rather than conduct typical transactions, the model of risk management must be appropriately tailored. Trust is again the key factor. When a member of the public makes the transition from ordinary citizen to ‘player' on a gaming site, it is vital to ensure that they are aware of the official rules of the specific game. Payouts and prizes, and the procedure for claiming them, must fully conform to the official literature set out by the gaming site. There should be no cases of ambiguity as this is a sure-fire way of discrediting a brand and losing player trust and thus, their custom.

To become an online participant in lotteries and other gaming sites an individual must disclose their sensitive details; this is very often the only means by which one can become a ‘player'. Being able to trust a lottery or gaming site with sensitive details should, therefore, be the foremost concern of a player as there is little point in worrying about payout procedure when compromised details could mean a bigger loss than any potential gain.

The WLA's Security Control Standard takes the above factors into consideration- perfectly illustrating how the security of data can be adapted to a unique business situation.

BASIC PROCESSES
Studying the information security standards horizontally, a number of basic processes/steps that lead to the identification of information security requirements are:

  • Step 1: Business impact analysis-Each business process is recorded and analyzed in terms of business impact from the realization of a possible security threat.

The business must answer a number of questions to calculate the impact of security breaches, including:

- How much would this cost the business in monetary terms?

- What would be the indirect costs (e.g., from reputation loss) if information is sold?

- What would the legal implications be?

Business processes are then prioritized based on an impact scale that identifies the most critical issues.

  • Step 2: Risk analysis-During this process, the possibility for the occurrence of a security incident is calculated, based on a database of security weaknesses. The risk analysis takes into account technical and procedural parameters, such as:

- Are there technical controls in place to safeguard customer data?

- Do procedures exist to complement the technical security controls?

  • Step 3: Risk management-The result of the risk analysis is a prioritization of risk in relation to the impact level (the result of the business impact analysis) and the identification of possible security measures for addressing the risk. The risk management process-the selection of appropriate security measures for addressing the risk or for risk transferring or acceptance-is determined by the management of the organisation.
  • Step 4: ISMS implementation-After the controls have been selected, they should be correlated under a common information security management system (ISMS). This correlation requires deep understanding of the operation of the organisation; consideration of human, cultural, technical, business and external factors; and continuous improvements.

Business Model for Information Security
One of the most recent information security frameworks that addresses information security from a business point of view is ISACA's BMIS.

The following definitions of the BMIS elements (derived from An Introduction to the Business Model for Information Security) are necessary for understanding how BMIS works:

  • Organization design and strategy-An organization is a network of people, assets and processes interacting with each other in defined roles and working toward a common goal.
  • People-The people element represents the human resources and the security issues that surround them. It defines who implements (through design) each part of the strategy. It represents a human collective and must take into account values, behaviors and biases.
  • Process-Process includes formal and informal mechanisms (large and small, simple and complex) to get things done.
  • Technology-The technology element is composed of all of the tools, applications and infrastructure that make processes more efficient.

To understand the operation of BMIS in practice, it is important to study the links connecting organization design and strategy, people, process, and technology.

CONCLUSION
Information security will be understood, provide added value and effectively contribute to the operation of an organization only if it is designed and implemented as a core ingredient of the business strategy. Stakeholder, shareholder and customer trust are the key ingredients of information security; organizations from all sectors should identify such key ingredients in order to provide a business definition to information security.

More Stories By Christos K. Dimitriadis

Christos K. Dimitriadis, Ph.D., CISA, CISM, is international vice president of ISACA and head of information security at INTRALOT S.A, a Greece-based multinational supplier of integrated gaming and transaction processing systems.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


@MicroservicesExpo Stories
Much of the value of DevOps comes from a (renewed) focus on measurement, sharing, and continuous feedback loops. In increasingly complex DevOps workflows and environments, and especially in larger, regulated, or more crystallized organizations, these core concepts become even more critical. In his session at @DevOpsSummit at 18th Cloud Expo, Andi Mann, Chief Technology Advocate at Splunk, will show how, by focusing on 'metrics that matter,' you can provide objective, transparent, and meaningfu...
Last week I had the pleasure of speaking on a panel at Sapphire Ventures Next-Gen Tech Stack Forum in San Francisco. Obviously, I was excited to join the discussion, but as a participant the event crystallized not only where the larger software development market is relative to microservices, container technologies (like Docker), continuous integration and deployment; but also provided insight into where DevOps is heading in the coming years.
Wow, if you ever wanted to learn about Rugged DevOps (some call it DevSecOps), sit down for a spell with Shannon Lietz, Ian Allison and Scott Kennedy from Intuit. We discussed a number of important topics including internal war games, culture hacking, gamification of Rugged DevOps and starting as a small team. There are 100 gold nuggets in this conversation for novices and experts alike.
The notion of customer journeys, of course, are central to the digital marketer’s playbook. Clearly, enterprises should focus their digital efforts on such journeys, as they represent customer interactions over time. But making customer journeys the centerpiece of the enterprise architecture, however, leaves more questions than answers. The challenge arises when EAs consider the context of the customer journey in the overall architecture as well as the architectural elements that make up each...
In a crowded world of popular computer languages, platforms and ecosystems, Node.js is one of the hottest. According to w3techs.com, Node.js usage has gone up 241 percent in the last year alone. Retailers have taken notice and are implementing it on many levels. I am going to share the basics of Node.js, and discuss why retailers are using it to reduce page load times and improve server efficiency. I’ll talk about similar developments such as Docker and microservices, and look at several compani...
Admittedly, two years ago I was a bulk contributor to the DevOps noise with conversations rooted in the movement around culture, principles, and goals. And while all of these elements of DevOps environments are important, I’ve found that the biggest challenge now is a lack of understanding as to why DevOps is beneficial. It’s getting the wheels going, or just taking the next step. The best way to start on the road to change is to take a look at the companies that have already made great headway ...
In 2006, Martin Fowler posted his now famous essay on Continuous Integration. Looking back, what seemed revolutionary, radical or just plain crazy is now common, pedestrian and "just what you do." I love it. Back then, building and releasing software was a real pain. Integration was something you did at the end, after code complete, and we didn't know how long it would take. Some people may recall how we, as an industry, spent a massive amount of time integrating code from one team with another...
From the conception of Docker containers to the unfolding microservices revolution we see today, here is a brief history of what I like to call 'containerology'. In 2013, we were solidly in the monolithic application era. I had noticed that a growing amount of effort was going into deploying and configuring applications. As applications had grown in complexity and interdependency over the years, the effort to install and configure them was becoming significant. But the road did not end with a ...
I have an article in the recently released “DZone Guide to Building and Deploying Applications on the Cloud” entitled “Fullstack Engineering in the Age of Hybrid Cloud”. In this article I discuss the need and skills of a Fullstack Engineer with relation to troubleshooting and repairing complex, distributed hybrid cloud applications. My recent experiences with troubleshooting issues with my Docker WordPress container only reinforce the details I wrote about in this piece. Without my comprehensive...
As the software delivery industry continues to evolve and mature, the challenge of managing the growing list of the tools and processes becomes more daunting every day. Today, Application Lifecycle Management (ALM) platforms are proving most valuable by providing the governance, management and coordination for every stage of development, deployment and release. Recently, I spoke with Madison Moore at SD Times about the changing market and where ALM is headed.
The goal of any tech business worth its salt is to provide the best product or service to its clients in the most efficient and cost-effective way possible. This is just as true in the development of software products as it is in other product design services. Microservices, an app architecture style that leans mostly on independent, self-contained programs, are quickly becoming the new norm, so to speak. With this change comes a declining reliance on older SOAs like COBRA, a push toward more s...
Small teams are more effective. The general agreement is that anything from 5 to 12 is the 'right' small. But of course small teams will also have 'small' throughput - relatively speaking. So if your demand is X and the throughput of a small team is X/10, you probably need 10 teams to meet that demand. But more teams also mean more effort to coordinate and align their efforts in the same direction. So, the challenge is how to harness the power of small teams and yet orchestrate multiples of them...
Many private cloud projects were built to deliver self-service access to development and test resources. While those clouds delivered faster access to resources, they lacked visibility, control and security needed for production deployments. In their session at 18th Cloud Expo, Steve Anderson, Product Manager at BMC Software, and Rick Lefort, Principal Technical Marketing Consultant at BMC Software, will discuss how a cloud designed for production operations not only helps accelerate developer...
SYS-CON Events announced today that Peak 10, Inc., a national IT infrastructure and cloud services provider, will exhibit at SYS-CON's 18th International Cloud Expo®, which will take place on June 7-9, 2016, at the Javits Center in New York City, NY. Peak 10 provides reliable, tailored data center and network services, cloud and managed services. Its solutions are designed to scale and adapt to customers’ changing business needs, enabling them to lower costs, improve performance and focus inter...
In the world of DevOps there are ‘known good practices’ – aka ‘patterns’ – and ‘known bad practices’ – aka ‘anti-patterns.' Many of these patterns and anti-patterns have been developed from real world experience, especially by the early adopters of DevOps theory; but many are more feasible in theory than in practice, especially for more recent entrants to the DevOps scene. In this power panel at @DevOpsSummit at 18th Cloud Expo, moderated by DevOps Conference Chair Andi Mann, panelists will dis...
Much of the discussion around cloud DevOps focuses on the speed with which companies need to get new code into production. This focus is important – because in an increasingly digital marketplace, new code enables new value propositions. New code is also often essential for maintaining competitive parity with market innovators. But new code doesn’t just have to deliver the functionality the business requires. It also has to behave well because the behavior of code in the cloud affects performan...
Struggling to keep up with increasing application demand? Learn how Platform as a Service (PaaS) can streamline application development processes and make resource management easy.
If there is anything we have learned by now, is that every business paves their own unique path for releasing software- every pipeline, implementation and practices are a bit different, and DevOps comes in all shapes and sizes. Software delivery practices are often comprised of set of several complementing (or even competing) methodologies – such as leveraging Agile, DevOps and even a mix of ITIL, to create the combination that’s most suitable for your organization and that maximize your busines...
Digital means customer preferences and behavior are driving enterprise technology decisions to be sure, but let’s not forget our employees. After all, when we say customer, we mean customer writ large, including partners, supply chain participants, and yes, those salaried denizens whose daily labor forms the cornerstone of the enterprise. While your customers bask in the warm rays of your digital efforts, are your employees toiling away in the dark recesses of your enterprise, pecking data into...
You deployed your app with the Bluemix PaaS and it's gaining some serious traction, so it's time to make some tweaks. Did you design your application in a way that it can scale in the cloud? Were you even thinking about the cloud when you built the app? If not, chances are your app is going to break. Check out this webcast to learn various techniques for designing applications that will scale successfully in Bluemix, for the confidence you need to take your apps to the next level and beyond.