CISA+Domain+2+Cyvitrix+ +updated+2024
CISA+Domain+2+Cyvitrix+ +updated+2024
com - ALL Rights are Reserved - Based on Latest CISA CRM v28
[email protected]
Cyvitrix.com
Certified Information
System Auditor Training
Domain 2 – Governance of IT
CYVITRIX - ALL RIGHTS RESERVED ©
124
WWW.CYVITRIX.COM
Domain 4 : IS
Domain 5 : Protection
Operations and
of Information Assets
Business Resilience
(26%)
(26%)
About Domain 2
Domain 2 represents 17% of the questions on the CISA exam
(approximately 25 questions).
Content
1. IT Governance and corporate structure and responsibilities
2. IT Key frameworks and Enterprise Architecture and ways to assess maturity
3. IT Management
4. IT Management practices
5. Quality assurance
130
What is Governance
Governance is a set of practices to set the strategic direction of the organization
Governance sets the goals for management to achieve and tackle
Through Governance, there should be a way where all stakeholders can provide input in decision-making
processes, the thing which leads to objective achievement and value creation.
Governance of any function aims to manage and use resources to support the interest of stakeholders.
Governance is the Board of Directors’ responsibility
Leadership, structure, policies and standards, and monitoring are all elements of effective governance.
131
Governance vs Management
• Senior Management and Board of • Management roles, oversee the
directors' role day-to-day operations
• Setting the direction and the • Develop the plans which help to
based-on Business requirements achieve the outcomes of the
• Set the overall Business Strategy strategy
• Monitor and evaluate the • Execute the plans, and provide
performance feedback
• Set the strategy • Ensure the alignment with
Business requirements
Governance Management
132
Governance outcomes
Accountability roles,
Governance is Directors IT Strategy should be
responsibilities and
and Senior management Stakeholders input developed on the basis
authorities, need to be
role of business strategy.
defined
133
Benefits of Governance
IT Resource Performance Portfolio Compliance
Service management
Management Measurement Management Management
• Track and monitor • Monitor IT • Decide to invest or • Consider legal, • Align with business
IT inventory of all resources and not invest based on contractual and requirements, IT is
resources benchmark it with strategic direction regulatory service provider,
• Manage risks predefined of the organization requirements into and business is the
related to IT indicators processes consumer
(generally accepted
standards and
peers
benchmarking)
• Analyze monitoring
results, and take
actions to improve
performance
134
135
Information Security
136
Information Security
A management function in any organization
The goal is to safeguard information assets and to handle risk efficiently.
Information Security goal is to maintain Confidentiality, Integrity, and availability of assets
Help organizations take advantage of opportunities while mitigating information risk.
Like any function, Information Security management should align with Business requirements and strategy
The Security strategy should be developed based on the Business Strategy
The Security Program should be developed to implement the strategy requirements
Without Senior management sponsorship, Information Security governance will not be effective
Senior management states the business requirements, if no engagement, then there is no alignment
Without Senior management sponsorship, no budget will be allocated, and no support will be given
137
138
Information Security
Incident Business
Security Security Policies Security Risk Security Integration with Vendor Compliance
Management and continuity
Governance development Management Awareness IT/Business Management Management
guidance management
139
140
141
SABSA
SABSA (Sherwood Applied Business Security Architecture) is a framework for developing risk-driven
enterprise security architectures.
SABSA adopts a risk-driven approach to security architecture, aligning security measures with the
organization's business objectives and risk tolerance. It emphasizes understanding and mitigating
business risks through adequate security measures.
SABSA strongly emphasizes understanding the business context and aligning security measures
with business goals and strategies. It aims to integrate security into the organization's overall
business architecture, ensuring that security supports and enables business objectives.
SABSA utilizes a layered architecture model comprising six layers: Contextual, Conceptual, Logical,
Physical, Component, and Operational. Each layer represents a different level of abstraction and
guides how security requirements and solutions can be designed and implemented.
SABSA emphasizes the importance of governance and assurance mechanisms to ensure the
effectiveness of security measures and ongoing alignment with business objectives.
SABSA
Different Perceptions
Enterprise Architecture
EA can be Technology-driven EA or
Business-driven EA
CYVITRIX.COM - ALL RIGHTS RESERVED
148
Policies
Policies
Reflect management intention, which each function in the organization should create based on the
situation.
define acceptable behavior and speak in high-level, simple language tailored to most audiences.
set the organization’s tone to reflect management intention; the highest management should sign this
document.
Each policy statement should state only one mandate, written in clear and straightforward language.
Policy document defines responsibilities and supports goals stated in strategy.
Policy needs to be regularly reviewed (At least every year)
Should be communicated to the policy audience
The original approver should approve exceptions for the policy statement.
No control should be introduced until mandated by Policy or Regulation
Policies
• Directly traceable to strategy elements
• Broad enough to not require regular revision but should be periodically reviewed
• Approved at the highest level
• Pave the way for effective implementation
Attributes of Good Policy
◦ Should capture the intent, expectations, and direction of management
◦ Should state only one general security mandate
◦ Must be clear and easily understood
◦ Includes just enough context to be useful
◦ Rarely number more than two dozen in total
Example of Policies
Human Resource Policy
IT Service Policy
Security Policy
Access Control Policy
Vendor management Policy
AUP (Acceptable Use Policy)
Code of Conduct Policy
TOP DOWN
Top-down approach
CYVITRIX - ALL RIGHTS RESERVED ©
154
Bottom-Up
Could lead to
Consider business unit inconsistency across Could miss some
requirements multinational strategic objectives
organization
Bottom-up approach
CYVITRIX - ALL RIGHTS RESERVED ©
155
Standards
Standards
Medium-level “extra detailed and technical” document
Defines requirements to ensure common understanding and follow the policy
Provides the basis for measurement
Standard is subject to change when the situation changes “new requirements or regulation.”
Could need to be reviewed more frequently.
Tell you what to configure/do/perform/follow – Policy defines what is needed
The baseline differs from the standards; the baseline defines the minimum requirements.
Standards
• Provide measurement for compliance
• Govern procedure and guideline creation
• Set security baselines
• Reflect acceptable risk and control objectives
• Act as criteria for evaluating acceptable risk
• Are unambiguous, consistent, and precise
• Are disseminated to those governed by them and those impacted
Standard Examples
Software Development Standards: These standards define the processes, tools, and techniques
that should be used during software development. They ensure that software is developed
efficiently, securely, and highly quality.
Network Security Standards define the requirements for securing an organization's network
infrastructure. They may include firewall requirements, intrusion detection and prevention
systems, and other security controls.
Access Control Standards: These standards define the requirements for controlling access to an
organization's systems and data. They may include requirements for authentication, authorization,
and other access control mechanisms.
Baseline
A baseline is a minimum level of security that an organization sets for its systems, applications,
and infrastructure.
A baseline defines the minimum-security requirements that must be met by all systems,
applications, and infrastructure components to ensure a consistent level of security across the
organization.
For example, an organization may establish a baseline that includes basic security controls such
as antivirus software, firewalls, and regular updates and patches.
A security standard, on the other hand, may include additional controls such as intrusion
detection and prevention systems, data encryption, and access controls.
Summary
Policies Standards Controls
Part of security
Governance tools Management tools
architecture
PROCEDURES
Low-level, step-by-step & detailed guide to follow to apply the standard.
implement the intent of the policy.
The subject is to be changed entirely if the process is changed.
If the way of doing the task changes, the procedure needs to be reviewed.
Compliance is mandatory.
Example of Procedures
To change password:-
3. Type the password that meets the standard at the first box
5. Press ok
GUIDELINES
Optional document, provide recommendations, and compliance might not be mandatory.
Can be used without clear standards, as it provides insight into best practices.
Usually, it defines the best practices.
For example, the password should meet the following criteria, but you still can use an easy-to-guess
password.
To achieve compliance with your organization, you need to understand cultural differences and
mindsets regarding guidelines; some companies treat specific guidelines as operational standards
(Example Center of Internet Security CIS)
Documents Maintenance
Review of Documents
Policies and standards should be reviewed on a regular basis, typically every one to three years,
depending on the nature of the policy or standard and the regulatory requirements that apply.
A review team should be established to conduct the review. The team should be composed of
individuals with relevant expertise and experience and should include representatives from key
stakeholder groups.
The review team should establish criteria for evaluating the effectiveness of the policy or
standard, including its relevance, accuracy, completeness, and clarity. The criteria should be
documented and communicated to relevant stakeholders.
The recommendations made by the review team should be reviewed and approved by the
appropriate stakeholders, such as senior management or the board of directors. The approval
process should be documented and communicated to relevant stakeholders.
Types of documentations
• Policies and standards, which form the basis for information risk management.
• Procedures and guidelines are used for security awareness training and education.
• Risk analysis and recommendations determine risk treatment choices and controls.
PROPERTIES OF GOOD
DOCUMENTATIONS
• Assigned owner
• Approved and Communicated
• Reviewed Periodically
• Well Protected according to the classification label
• Large enterprises have document management system, so Information security manager does
not maintain the custodianship of security documentation
Documents maintenance
• The official ISO/IEC 27001 standard itself outlines the requirements for establishing,
implementing, maintaining, and continually improving an ISMS. Clause 7.5 specifically
addresses the control of documents, including requirements for document approval, review,
distribution, and changes.
• In NIST 800-53 SP, Control SA-5 (Information System Documentation)
• Version Control and Document Information are required
• Changes in Higher level document should trigger updates to the related documents, for
example policies and standards
• Approval, owner, last update date need to be clearly mentioned
175
175
176
176
177
177
Role of auditor
• Identify legal requirements, to assure business compliance and
document it.
• Review regulation related procedures that support the
compliance, which can be used as check list.
• Reviewing an organization's policies, procedures, and controls to
Ensure they meet legal and regulatory requirements.
• Provide guidance to management on legal and regulatory issues
related to information systems. This may include helping to
develop policies and procedures to ensure compliance with
applicable laws and regulations. 178
178
Risk Management
What is Risk
Risk is the effect of uncertainty on objective
Risk can be measured objectively or subjectively depending on the
asset that we assess risks related to it
Risks are tied to assets. In Risk management, we try to assess the risk
impact and probability, decide on a proper risk response to reduce
this risk to an acceptable level, and monitor the risk
Risk is a product of likelihood and impact
Risk Assessment
TM Sc.
Communication and
Likelihood Existing
Risk Analysis controls
Impact Risk Monitoring &
Risk Reporting
Compensating
(Risk Register)
Appetite
Review
(Risk Acceptance Form) Risk Evaluation (KRI)
Tolerance
Risk Levels
Risk Identification
Risk Scenario
Group’s effort to do brainstorm and develop different risk scenarios
Evaluate vulnerabilities based on available and realistic threats
Identify the corresponding risks
Could be
◦ Top Down -> consider Business Goals when thinking about possible issues
◦ Bottom Up -> hypothetical scenarios
Risk Analysis
Cascading Risk
Cascading risk refers to the phenomenon where the failure or disruption in one system or sector
triggers a chain reaction of failures or disruptions in interconnected systems or sectors.
Cascading risk occurs due to the interdependencies and interconnectedness between various
systems, organizations, or sectors.
A disruption in one area can propagate and impact others.
The impact of cascading risk tends to amplify as failures cascade through interconnected
systems.
The initial failure can lead to secondary failures, creating a domino effect, potentially causing
widespread disruption or systemic collapse.
Semi-Quantitative Approach
Semi-quantitative risk analysis combines qualitative and
quantitative techniques.
Risks are evaluated using qualitative scales or predefined
numerical ranges.
Expert knowledge and subjective assessments are used, which
may result in less precision and objectivity compared to fully
quantitative analysis.
Limited quantitative data, such as historical incidents or basic
probabilities, may be utilized, but complex mathematical
models are not heavily relied upon.
Semi-quantitative risk analysis aids in effective communication
by providing a structured framework and visual representation
of risk levels, enhancing stakeholder understanding.
Risk Managing/response
Mitigation • Risk is unacceptable; use security controls to reduce the risk level to an acceptable level.
Accept Risk / Risk • The loss is within acceptable range, taking certain risks is part of the business challenge to
retention, Bearing, Keeping make revenue.
• Cascade the risk to another party by outsourcing insurance, but this does not remove
Risk Transfer / Risk Sharing accountability or liability.
• Outsourcing is transfer, Insurance is sharing – but usually there no difference in daily use
Risk Avoidance • We will remove the source of the risk by terminating the process which the risk sourced from,
for non-business priorities.
Risk Reporting
Risk reporting should be tailored to audiences
Risk should be documented in Risk register
Accepted risk should undergo formal
acceptance process through related form such
as RAF “RISK ACCEPTANCE FORM”
Identified Risk should have identified owner.
Risk Register
It is a central repository for all risk-related information, and it provides a structured approach for
identifying, assessing, and managing risks.
The risk register is a living document that requires regular updates as new risks are identified, existing
risks evolve, and mitigation strategies are implemented or adjusted. It should be reviewed and updated
throughout the project or organizational lifecycle.
The risk register is a core component of risk management processes and integrates with other risk
management activities, such as risk assessment, analysis, and response planning. It serves as a
reference for decision-making, resource allocation, and communication related to risks.
The risk register facilitates collaboration and communication among stakeholders by providing a shared
understanding of risks and their management. It allows stakeholders to contribute to risk identification,
analysis, and response planning.
The risk register serves as a historical record of risks, their management, and outcomes. It supports
reporting to relevant stakeholders, regulatory compliance, and lessons learned for future projects or
initiatives.
CYVITRIX - ALL RIGHTS RESERVED ©
204
KPI vs KRI
SPECIFIC MEASURABLE
MEASURABLE ACCURATE
ATTAINABLE RELEVANT
RELEVENT SENSITIVE
TIME BOUND
• KRIs should provide • KRIs should provide • KRIs should be • KRIs should be based
information that can information in a presented in a clear on traceable,
be used to inform risk timely manner, using and concise format verifiable, and
management up-to-date data that is easily auditable data,
decisions and trigger collected regularly to understood and ensuring their
appropriate actions ensure the relevance interpreted by reliability and
or risk mitigation and currency of risk relevant accuracy for
plans. information. stakeholders, compliance purposes
facilitating informed and demonstrating
decision-making. adherence to
regulatory
requirements or
contractual
obligations.
Examples of KRI
The number of cybersecurity incidents or breaches is a common KRI for organizations to track. This could
include measures such as the number of attempted attacks, the number of successful attacks, or the
number of data breaches.
KRIs can also be used to track compliance with regulations or internal policies. For example, an
organization may track the number of compliance violations, the severity of those violations, or the
number of fines or penalties incurred.
KRIs can also be used to track operational metrics such as the number of customer complaints, the rate
of product defects, or the number of supply chain disruptions.
Every KRI is originally a KPI, but not every KPI can serve as KRI
KRI Types
Leading KRIs
◦ Forward-looking indicators that provide early warning signs of potential risks or problems.
◦ Used to predict future outcomes based on current trends or patterns.
◦ Used to monitor risk drivers and to identify potential risks before they materialize.
◦ Examples include customer complaints, employee turnover rate, and number of near-misses in workplace
safety incidents.
Lagging KRIs
◦ Backward-looking indicators that measure the actual results or outcomes of past events or activities. Used to
evaluate the effectiveness of risk management strategies and to identify areas for improvement.
◦ Used to measure the impact of risks that have already occurred.
◦ Examples include financial losses due to fraud, and number of customer complaints that have already been
resolved.
Security Controls
Security Controls?
Help in minimizing security risks to assets.
Technical and nontechnical methods.
The cost of control and amount of investment should be relative to the value
of the asset.
Security investment cannot be linked to ROI (Return on Investment), but
there is ROSI (Return on Security investment)
Controls can be categorized in terms of function into four types (Preventive,
Detective, Deterrent, and Corrective)
Controls Classification
Class Func on
Preventive •
•
Detect problems before they arise.
Monitor both opera on and inputs.
• A empt to predict poten al problems before they occur and make adjustments.
• Prevent an error, omission, or malicious act from occurring.
Detective • Detect and report the occurrence of an error, omission, or malicious act.
Corrective •
•
Minimize the impact of a threat.
Remedy problems discovered by detec ve controls.
• Correct errors arising from a problem.
Adversary Uses Threat To initiate Attack Exploit Flaw Asset Cause Impact
Detective Preventive
Trigger response
Summary
Security controls are safeguards used to protect assets and minimize security risks.
Security controls can be categorized based on their function: preventive, detective, or corrective.
◦ Preventive controls aim to prevent attacks or problems from occurring, and some can also detect and prevent
attacks.
◦ Detective controls focus on detecting attacks or malicious activities.
◦ Corrective controls are implemented after an attack to minimize the impact and restore systems or services.
◦ Deterrent controls are used to reduce the likelihood of an attack by discouraging potential attackers.
Security controls can be used before, during, or after an attack, depending on their purpose and
effectiveness.
The cost of security controls should be considered relative to the value of the asset, and a cost-
benefit analysis should be performed.
Return on security investment can include benefits such as customer retention and gaining a
competitive advantage.
Detective Controls
SIEM (Security Information and Event Management) solutions: These systems collect and analyze security-
related data from various sources in real-time, helping to identify and respond to potential threats.
Intrusion detection systems (IDS): These systems monitor network or system activities for malicious
activities or policy violations and generate alerts when such activities are detected.
Vulnerability scanners: Tools that scan systems and networks to identify security weaknesses that could be
exploited by attackers.
Audits: Formal reviews and examinations of an organization’s systems, processes, and controls to ensure
compliance with security policies and regulations.
Security reviews: Regular evaluations of security policies, procedures, and controls to ensure they are
effective and up-to-date.
Motion sensors: Devices that detect physical movement within a specified area, often used to detect
unauthorized physical access.
Video cameras: Surveillance equipment used to monitor and record activities within or around a facility,
helping to detect and investigate security incidents.
Deterrent Controls
Login banners: Messages displayed on login screens that inform users of security policies and
potential penalties for unauthorized access, discouraging unauthorized attempts.
Monitoring tools: Software or systems that continuously observe network or system activities to
detect and alert on suspicious behavior.
Security awareness programs: Training and educational initiatives designed to inform employees
about security risks and best practices, reducing the likelihood of human error.
Fences: Physical barriers that restrict unauthorized access to a facility, acting as a visible
deterrent to potential intruders.
Warning banners: Signs or notifications that alert individuals to the presence of security
measures, such as surveillance cameras or alarm systems, to discourage unauthorized actions.
Preventive Controls
Firewalls: Hardware or software systems that monitor and control incoming and outgoing
network traffic based on predetermined security rules, preventing unauthorized access.
Antivirus software: Programs designed to detect, prevent, and remove malware, protecting
systems from infections.
EDR (Endpoint Detection and Response) solutions: Advanced tools that continuously monitor
end-user devices to detect and respond to cyber threats in real-time.
Quality assurance processes: Procedures that ensure security measures are integrated into the
development and deployment of systems and applications, preventing vulnerabilities from being
introduced.
Corrective Controls
Backup and recovery solutions: Systems and processes for regularly backing up data and
restoring it in the event of data loss or corruption, ensuring business continuity.
Network isolation: Techniques for segmenting networks to limit the spread of an attack and
contain damage, helping to prevent the escalation of security incidents.
Incident response plans: Detailed strategies and procedures for identifying, managing, and
mitigating security incidents, reducing their impact and facilitating quick recovery.
Fire suppression systems: Equipment and processes designed to detect and extinguish fires,
protecting physical assets and minimizing damage from fire-related incidents.
Control Objective
Compensating Controls
Countermeasures
Requirements
Dictate what needs to be achieved to ensure security, functionality, and
compliance.
They guide the design and implementation of controls.
Control Objectives
Control objective is the expected result to be achieved by implementing controls.
The role of control is to address risks and help deal with them.
Performance Indicators (PIs) should be defined during the control design and
control performance should be continuously monitored using the performance
indicators to assess control performance.
Compensating Control
Compensating control is employed when the utilization of a preventive control is not
feasible for any reason. For instance, if regulations prohibit the use of a specific
control, alternative measures are sought to achieve the intended security benefits.
Examples
While best practices dictate against using shared accounts, certain systems may lack
the ability to create named accounts. In such cases, compensating controls, such as
additional monitoring or access restrictions, are implemented to mitigate associated
risks.
This could involve password security, where the password is split in half. To perform
an action, two individuals must present their respective halves of the password,
enhancing security through a dual-authentication process.
Countermeasures
Designed to
Counter a specific
issue that is
there!
The goal is to
Reduce the Reactive
Impact
Defence in Depth
Defence in Depth
Defence in depth is a comprehensive security strategy that involves
using multiple layers of security controls to protect an organization's
critical resources.
By using multiple layers of security, organizations can improve their
overall security posture and reduce the risk of a successful attack.
it is essential to note that defense-in-depth is not a fool-proof
strategy and that no security measure can provide 100% protection
against all threats. Therefore, it is necessary for organizations to
continuously evaluate and improve their security measures to stay
ahead of evolving threats.
Layers Examples
Physical Security: Locks, guards, and surveillance.
Network Security: Firewalls, intrusion detection systems, and secure access
controls.
Endpoint Security: Antivirus software, patch management, and secure
configurations.
Application Security: Secure coding practices, application firewalls, and
regular security testing.
Data Security: Encryption, access controls, and data loss prevention.
User Security: Training, awareness programs, and multi-factor authentication.
Policy and Procedures: Security policies, incident response plans, and
compliance.
Host Security
◦ Antivirus software, operating system patches, and intrusion prevention systems can be used to protect
individual systems from attack.
Data Security
◦ Data encryption for data at rest and use of digital rights management.
User education
◦ Help improve the organization's security posture by helping users recognize and avoid potential security
threats, such as phishing attacks or social engineering.
Management of it
Network
Development Linux/Microsoft
Security
Application
Production Database
Security
Access
QA&QC Backup
Management
Monitoring
CYVITRIX.COM - ALL RIGHTS RESERVED
247
Service
Service Strategy Service Design
Transition
Service
Continual
Itil framework
Operation
Service
Improvement for service
CYVITRIX.COM - ALL RIGHTS RESERVED management
248
functions
Personnel Security
Personnel Security?
It protects an organization's information assets by ensuring that employees, contractors, and third-
party service providers are trustworthy and have appropriate access privileges.
Personnel security concerns about people accessing the organization's information rather than the
technology or systems that store or transmit that information.
Personnel security requires collaboration efforts between security functions and human resources
functions in the organization.
Outsourcing
Benefits of Outsourcing
Outsourcing is the practice of contracting or delegating certain business functions, processes, or
tasks to external third-party organizations or individuals.
Instead of handling these activities in-house, companies transfer the responsibility and
operation of specific functions to external entities.
The outsourcing arrangement typically involves hiring a specialized service provider or vendor
that has expertise in the particular area being outsourced.
This allows the company to leverage the provider's skills, resources, and economies of scale to
improve operational efficiency, reduce costs, and focus on core business activities.
The decision to outsource should be based on a careful analysis of the specific requirements,
cost-benefit considerations, and the potential impact on the organization's overall operations
and strategic objectives.
Benefits of Outsourcing
• By outsourcing certain functions, companies can reduce operational costs
Cost Savings associated with hiring and training in-house staff, maintaining infrastructure,
and managing overhead expenses.
• Outsourcing allows companies to tap into the specialized skills and knowledge
Access to Expertise of external service providers who have experience and expertise in specific
areas.
Scalability and • Outsourcing provides the ability to scale operations up or down quickly based
on business needs, without the need for significant investments in
Flexibility infrastructure or personnel.
Outsourcing Considerations
You should not outsource:-
Core functions
Specialized Function that is strategic or critical
Functions cannot be outsourced due to regulatory requirements
What you can achieve locally with lower risk and cost compared to
outsourcing!
Outsourcing Steps
1. Define the function that can be outsourced
2. Define Service Level Requirement
3. Cost-benefit analysis
4. Bidders screening and RFP drafting
5. Draft the contractual requirements
o SLA / Security and Availability
o Right to Audit
o Terms and Conditions
Outsourcing Risks
• Risk of data breaches, unauthorized access, or mishandling of sensitive data. Assess the
Data Security and Privacy risks security measures and data protection practices of the outsourcing provider.
Communication and Cultural • Language barriers, time zone differences, and cultural nuances may pose challenges.
Differences risks Implement effective communication strategies, regular interactions, and cultural sensitivity.
Dependency on the Service Provider • High degree of dependency on the provider. Conduct due diligence on their financial stability,
risks reputation, and reliability.
Outsourcing Risks
• Ensure compliance with laws, regulations, and contractual obligations. Consider data
Legal and Compliance risks protection, intellectual property rights, and industry-specific regulations.
• Ongoing monitoring, performance evaluation, and issue resolution required. Establish clear
Vendor Management challenges governance structures, regular reporting, and periodic performance reviews.
• Poor performance or unethical practices by the provider can harm the organization's
Reputation and Brand risks reputation. Conduct thorough background checks, obtain references, and monitor provider
behavior and performance.
Dependence on Single supplier • Using multiple suppliers and avoid using single source
for technology or service
Startup Software house can quit • Software Escrow agreement to help you get access to
the market source code if provider is not in market any more
SOC Report
Service Organization Control (SOC) – Changed in 2018 to “System Organization
Controls”
Cloud providers, ISPs, and Hosting companies can benefit from it, including AWS,
AZURE, GCP, STRIPE, PAYPAL, PAYONEER, SALESFORCE
When customers request the right to audit requests, service providers can send
a copy of their latest SOC audit report.
SOC report is a result of the SOC Audit
3 Types of SOC Report
SOC-2
• Addresses a service organization's controls that are relevant to their operations and compliance
• Report on controls for customers, include private info.
• 2 Types available (1 – examine 5 domains, 2 include additional attestation)
• Introduced by SSAE16
• Conducted every 6 months
SOC-3
• Is a public report of internal controls over security, availability, processing integrity, and confidentiality.
• Summary report on controls
• Publicly available
SOC 2 criteria's
The SOC 2 audit process includes five categories of Trust Services Criteria:
◦ Security (or Common Criteria)
◦ Availability
◦ Confidentiality
◦ Processing Integrity
◦ Privacy
These categories each cover a set of internal controls related to different aspects of
your information security program.
SOC Reports
Financial management
SERVICES of it & SECURITY
It Financial management
Focuses on managing the financial aspects of IT services, including budgeting, accounting, and cost
optimization.
IT services can represent a significant portion of a company's overall budget.
A. Shared cost -> easier to finance, but lead to user dissatisfaction
B. Charge-back -> pay-as-you-go charge on system use
C. Sponsor Pays -> governance challenge as sponsor pay for all then he may request more
authority, and it may purchase extra capacity that is not measured by IT. It is notorious
for Segregation of duties.
Help in aligning IT sepdning with business objectives, optimize IT cost by identify opportunities of cost
reduction and provide financial insight for the decision makers.
IT Portfolio Management
involves managing a portfolio of IT services, applications, and infrastructure to optimize the
delivery of IT services in support of business objectives.
The strategic goal is to determine the opportunities of investment, or would the organization
continue in certain investment.
Helps in adjusting investments via built-in feedback mechanisms, and Prioritizing IT investments
Effective IT portfolio management requires collaboration between IT and business stakeholders,
as well as a deep understanding of the organization's business objectives, IT service
requirements, and risk management strategies.
It capacity management
Focuses on ensuring that an organization's IT infrastructure and services have the necessary
capacity to meet current and future business requirements.
Ensure that the IT infrastructure and services are able to deliver the required level of
performance, availability, and scalability in a cost-effective manner.
Optimize the capacity utilization Helps to optimize the utilization of IT resources, such as servers,
storage, and network bandwidth, to minimize waste and reduce costs.
Identifying and mitigating capacity-related risks and assist in planning for future capacity
requirements.
It supplier management
Focuses on managing the relationships and contracts with IT suppliers and vendors.
Ensure that the organization's IT services are delivered effectively and efficiently by third-party
suppliers, and to manage the risks associated with outsourcing IT services.
Help to manage the contracts with IT suppliers, ensuring that they are aligned with the
organization's requirements and that the terms and conditions are met.
Effective IT Supplier Management requires collaboration between IT and procurement
departments
CAPEX
Capex, or capital expenditures, refers to the funds that a company spends on acquiring or
upgrading physical assets such as property, equipment, and infrastructure.
Capital expenditures are typically investments in long-term assets that are expected to generate
benefits for the company over a period of years.
Examples of capital expenditures include building a new factory, purchasing machinery or
equipment, or expanding a warehouse.
Companies often make decisions about capex spending based on factors such as the expected
return on investment, the company's financial position, and the overall business strategy.
opex
Opex, or operating expenses, refers to the costs that a company incurs in order to maintain its
day-to-day operations.
Examples of operating expenses include employee salaries and benefits, rent, utilities,
marketing and advertising expenses, and office supplies.
Unlike capex, which is typically a one-time expense, operating expenses are recurring and are
incurred on an ongoing basis.
Managing opex is an important aspect of financial management for companies, as it can impact
the company's profitability and cash flow.
Companies often seek to reduce operating expenses by optimizing processes, negotiating better
contracts with suppliers, and making other efficiency improvements.
ROI
ROI stands for Return on Investment.
It is a financial metric used to evaluate the profitability of an investment by comparing the amount of
return on the investment to the cost of the investment.
ROI is typically expressed as a percentage or a ratio.
A high ROI indicates that the investment is profitable, while a low ROI indicates that the investment is
not profitable.
ROI is commonly used by businesses and investors to assess the potential benefits of investing in a
particular project or asset, and to compare the profitability of different investment opportunities.
ROI for IT is not only financial, but it could also be non-financial as well
ROI Example
A company's investment in a new marketing campaign. Let's say the company spends $50,000
on a marketing campaign and as a result, generates $100,000 in new sales revenue. The net
return on investment would be $50,000, which is the revenue generated ($100,000) minus the
cost of the campaign ($50,000).
ROI = (Net return on investment / Total cost of investment) x 100%
ROI = ($50,000 / $50,000) x 100% = 100%
This means that for every dollar invested in the marketing campaign, the company gained $1 in
return.
ROSI
ROSI stands for Return on Security Investment.
ROSI measures the return on investment (ROI) specifically related to security spending
and is calculated by dividing the net return on security investment by the total cost of
the security investment.
The net return on security investment is the total value of the benefits gained from the
investment in security measures minus the total cost of the investment.
A high ROSI indicates that the security investment is delivering significant benefits
relative to its cost, while a low ROSI indicates that the investment may not be
providing sufficient value.
ROSI Example
The implementation of a new security system in a company's network infrastructure. Let's say the
company invests $100,000 in a new security system to prevent cyber attacks, and as a result, the system
helps prevent a major data breach that would have cost the company $1 million in damages.
ROSI = (Net return on security investment / Total cost of security investment) x 100%
ROSI = ($900,000 / $100,000) x 100% = 900%
This means that for every dollar invested in the security system, the company gained $9 in return. A
ROSI of 900% indicates that the investment in the security system was highly effective in reducing the
risk of a security breach and generated significant value for the company.
MATURITY ASSESSMENT
Maturity Frameworks
Maintaining consistency, efficiency and effectiveness of IT processes
requires the implementation of a process maturity framework.
Plan/do/check/act
Plan Check
Identify processes
to be re- Redesign Monitor and
engineered processes measure results
IT PERFORMANCE
MANAGEMENT
IT Performance Management
Performance metrics should be developed for monitoring
performance.
Performance metrics should be developed on basis expected
output.
Metrics should be regularly assessed for adequacy
Metrics should be Specific, Measurable, Achievable, Relevant and
time bound.
IT Balanced Scorecard • A process management evaluation technique that can be effectively applied
to assess IT functions and processes
(IT BSC) • Holistic view of IT, and help in alignment with Business
• The Process of diagnosis to establish the origins of events so that controls can
Root Cause Analysis (RCA) be developed to address these causes.
Quality assurance
and control
Quality Assurance
Process Oriented
Set standards and requirements
Prevent the defect from occurring
Preventive Control
Proactive
QA Specialist should not be from actual programming or coding team – Separation of
duties should be in place.
List and promote the specifications required on Product level, software, process and
compliance requirements, they issue the standard which should be applied by
developing team for example.
SELF READING
QMS process
Context of Planning the into the
the quality operational
Organization objectives process Improvement
ISO 12207
Standard for software life cycle processes. This standard defines a set of processes and activities
that are required for the development, operation, and maintenance of software. ISO/IEC 12207
provides a framework for the management of software projects and helps ensure that the
software meets the specified requirements and quality standards.
In-House
Acquisition Development
Process Process Maintenance
COBIT Framework
COBIT
Core
MODEL
PRM
Design Factors
COBIT implementation