National Information Security Policy and Guidelines | Ministry of Home Affairs
1.3. Principle 1: Meeting stakeholder needs6: A group of stakeholders includes any individual or
group affected by the current state or future state of a process, system, policy, etc. Stakeholder
analysis is the process of identifying stakeholders so that their input can ensure outcomes
match requirements. This is an important step in both project planning and risk management.
Failure to involve all stakeholders, including InfoSec and audit teams, usually results in less than
optimum outcomes at best. Worst case outcomes include failed projects or material audit
deficiencies. Successful stakeholder analysis results in maximizing benefits, minimizing risk to
or beyond expected outcomes, and optimizing resources. Further, ensuring integration of
business and information assurance requirements into the development or acquisition of a
solution is always preferable to trying to “hang” something onto a finished—but incomplete—
system, network, or a physical controls framework.
1.4. Principle 2: Covering the enterprise end-to-end: Information security is often applied as series
of point solutions, as defined in more detail in Principle 3. However, general application of
security and assurance best practices requires security reviews as part of all business processes
and IT development and implementation activities. This isn’t just a horizontal integration.
Rather, all levels of management must include InfoSec in every business strategic and
operational planning activity.
1.5. Principle 3: Applying a single integrated framework: Application of security controls is often a
point-and-shoot activity. Many organizations tend to fix specific issues without stepping back
and applying policies and controls that impact multiple vulnerabilities in network or
system attack surfaces. Designing a complete framework includes all aspects of information
storage, flow, and processing, providing a foundation for more efficient control
implementation.
1.6. Principle 4: Enabling a holistic approach: As support for developing an integrated framework,
it’s important to see information security as a set of related components: not as set of silos.
Each component is driven by enablers and other factors affecting organization risk. COBIT 5 for
Information Security provides a list of enablers and describes how they interrelate. Enablers
help organizations integrate operations and security into the outcomes of all principles defined
here. As always, this is done in a way to meet stakeholder requirements.
1.7. Principle 5: Separating governance from management: This principle establishes a line between
setting
objectives
and
measuring
outcomes.
According to COBIT 5 for Information Security:
“Governance ensures that stakeholder needs, conditions, and options are evaluated to
determine balances, agreed-on enterprise objectives to be achieved; setting direction through
prioritization and decision making; and monitoring performance and compliance against agreedon direction and objectives.”
While governance and management are separate functions performed by designated teams,
they must support each other. Governance defines outcomes and management implements
technology and processes to meet those outcomes. Governance then determines if outcomes
are met and provides feedback to help management make necessary adjustments.
6
http://www.techrepublic.com/blog/it-security/cobit-5-for-information-securitythe-underlying-principles/#.
NISPG - Version 5.0
Restricted
Page 235
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents