ASM2-Security-Nguyen Huu Loi
ASM2-Security-Nguyen Huu Loi
ASM2-Security-Nguyen Huu Loi
Student declaration
I certify that the assignment submission is entirely my own work and I fully understand the consequences of plagiarism. I understand that
making a false declaration is a form of malpractice.
Student’s signature
Grading grid
P5 P6 P7 P8 M3 M4 M5 D2 D3
Learning Outcomes and Assessment Criteria
P5 Discuss risk assessment M3 Summarise the ISO 31000 D2 Consider how IT security
procedures. risk management methodology can be aligned with
and its application in IT security. organisational policy,
P6 Explain data protection detailing the security impact
processes and regulations as M4 Discuss possible impacts to of any misalignment.
applicable to an organisation. organisational security resulting
from an IT security audit.
P7 Design and implement a security M5 Discuss the roles of D3 Evaluate the suitability of
policy for an organisation. stakeholders in the organisation the tools used in an
to implement security audit organisational policy.
P8 List the main components of an recommendations.
organisational disaster recovery
plan, justifying the reasons for
inclusion.
Table of content
Introduction…………………………………………………………………………………5
5.5 Explain Asset, threat and threat identification procedure, give example………………7
5.6 Explain the risk assessment procedure…………………………………………………9
5.7 List risk identification steps……………………………………………………………9
……………………………………………………………………………………………..10
P8 List the main components of an organisational disaster recovery plan, justifying the
reasons for inclusion……………………………………………………………………….21
8.4 Explain some of the policies and procedures that are required for business
continuity…………………………………………………………………….……………25
Conclusion………………………………………………………………………..……….27
Reference………………………………………………………………………………….28
List of figures
In this assignment, I will complete two duties. The first duty is to evaluate techniques for
controlling corporate IT security. In this assignment, I will address risk assessment
procedures, as well as data protection and regulation. In addition, I will describe the ISO
3100 risk management approach and its application in IT security. Another prerequisite is to
examine the potential impact of a security audit on organizational security. The next job
involves designing and implementing a security strategy for a company, as well as
demonstrating the essential components of an organizational disaster recovery plan. Because
stakeholders are a part of the company, I will address their role in putting security audit
findings into action.
LO3 Review mechanisms to control organisational IT security.
-Is problems that may endanger the stakeholders' products for the project. It is the potential
for a bad or undesired result. Risk is regarded as a prospective issue because it is something
that has never happened and may never happen.
- Risk assessment involves determining the damage that would result from an attack and the
likelihood that the vulnerability is a risk to the organization. Risk assessment can be done
using qualitative or quantitative risk calculation tools to help determine the risk likelihood
and risk impact.
- The aim of the risk assessment process is to identify hazards, remove them when needed,
or reduce the level of risk they pose by implementing management measures. You've made
the workplace safer and healthier by doing this.
5.5 Explain Asset, threat and threat identification procedure, give example
A. Asset
-Examples of assets include a worker's desktop computer, laptop, or company phone, as well
as the apps on such devices. Servers and other essential infrastructure are also advantageous.
B.Threat
- A threat is something that could potentially harm an asset, such as if it were to get lost,go
offline, or be accessed by an unauthorized person.
- Intentional risks include staff error, a technology failure, or an event that results in physical
injury, such a fire or a natural disaster. Examples of unintentional risks include employee
error, a technological breakdown, or a malicious insider stealing information.
Figure 7 Threat
C. Threat identification process.
- The threat identification approach looks into IT flaws and evaluates how likely they are to
allow access to your system. It is a crucial part of the risk management strategy for your
company. By recognizing threats, your business can take proactive action. Every stage that
is finished is recorded. The threat model for the application is in the created document.
- The three sorts of dangers are man-made, technical, and natural threats. Threat categories
including Auditing & Logging, Authentication, Authorization, Configuration Management,
Data Protection in Storage and Transit, Data Validation, and Exception Management are
defined by the Application Security Frame (ASF) and can be used to classify threats.
- Arranging threats that have been detected into profiles that provide more details, such as
the type of danger that has been recognized, the possibility that it will occur, any relevant
history, and the ramifications Preparation is key in threat assessments and emergency
management.
-The most hazardous and probable dangers are used to build emergency management
scenarios. The scenarios cover the initial alert, anticipated community impact, potential
trouble zones, damage response, limited resources, and potential consequences. These
hypothetical situations are continuously assessed using a variety of criteria and updated with
new data, ensuring that the threat analysis is always one step ahead of the actual threat.
• Risk Assessment
➢ Identification of risks
➢ Risk evaluation
➢ Risk impact
➢ Recommendation of risk-reducing measures
• Risk Mitigation
➢ Risk avoidance
➢ Risk mitigation
➢ Risk acceptance
➢ Risk transference
➢ Risk assessment
• Evaluation and Assurance
➢ Continuous risk assessment
➢ Periodic assessment
➢ Regulatory adherence
5.7 List risk identification steps
- There are five essential parts to the process of risk identification and management. The
stages involved include risk identification, analysis, assessment, treatment, and monitoring.
• Risk Identification
-Finding out what, where, when, why, and how something can affect a company's ability
to function is the aim of risk identification. As an example, a business in central California
would list "the possibility of wildfire" as a potential event that could interfere with
business operations.
• Risk Analysis
-In this phase, the likelihood of a risk event happening and the likely results of each
occurrence are both determined. Safety managers may look at the amount of rain that fell
in the previous 12 months and the extent of damage an organization may sustain if a fire
started, using the California wildfire as an example.
• Risk Evaluation
- According to importance and impact, each danger's level is compared and ranked. For
example, it may be necessary to weigh the effects of a potential mudslide against those
of a potential wildfire. The occurrence with the highest likelihood of occurring and
inflicting harm is ranked higher.
• Risk Treatment
- Risk response planning is another name for risk management. This step involves
developing risk mitigation strategies, preventative measures, and backup plans based on
the projected value of each risk. Risk managers may choose to store extra network servers
offshore in the event of a wildfire so that business operations can continue even if an
onsite server is damaged. The risk manager may also create plans for employee
assessments.
• Risk Monitoring
- Risk management is a continuous process that changes and grows over time. All known
and unknown threats can be covered by repeating and closely monitoring the procedures.
- This policy defines how to ensure that all personnel are aware of the importance of
security and behavioral expectations under the organization’s security policy. This policy
is specific to the User Domain and is relevant when you need to change organizational
security awareness behavior.
- This policy defines an organization-wide threat assessment and monitoring authority. You
should also include specific details regarding the LAN-to-WAN Domain and AUP
compliance in this policy.
B. Audience
-Establish who the information security policy's target market is. You can also choose which
groups of people are not included in the policy's scope (for instance, employees of a different
business unit whose security is managed separately might not be in the policy's reach).
-Help your management team to set a clear strategy and security goals. The following are
the main objectives of information security:
➢ Hierarchical pattern: A senior manager might be able to decide who gets access
to what information and to whom. The security policy of a senior manager may be
different from that of a lower employee. The scope of each organizational job's
control over data and IT systems should be outlined in the policy.
➢ Network security policy: Only specific logins requiring authentication, such as
passwords, biometrics, ID cards, or tokens, can grant users access to company
networks and servers. All systems need to be watched over, and every login attempt
needs to be documented.
E. Data classification.
- Data should be divided into categories like "top secret," "secret," "confidential," and
"public" according to the policy. Your objective while classifying data is:
+ Limiting access to sensitive data by those with lower clearance levels
+ To protect crucial data while avoiding the needless use of security measures for trivial
data.
-Data protection requirements require that systems that contain personal or sensitive data
adhere to organizational standards, best practices, industry compliance standards, and related
statutes. Most security requirements demand encryption, a firewall, and anti-malware
protection as a bare minimum.
➢ Data backup:
-According to accepted industry standards, encrypt backup data. Backup media must be
transported to a secure cloud storage facility or kept there safely.
➢ Movement of data:
-Only use secure methods to send data. Encrypt any data copied to portable devices or sent
over a public network.
-Inform your staff of the rules governing IT security. Training sessions should be held to
inform personnel about your security procedures and controls, such as data.
➢ Social engineering:
-Stress the risks of social engineering attacks (such as phishing emails). Such assaults should
be identified, stopped, and reported, and employees should be held responsible.
-A cable lock can be used to secure laptops. Documents that are no longer needed should be
shredded. Keep printer locations tidy to avoid papers falling into the wrong hands.
H. Encryption Policy.
-A data backup policy lays out the rules and procedures for making data backup copies. It is
crucial to a thorough approach to data protection, business continuity, and disaster recovery.
The main goals of a data backup policy are as follows:
+ Identifies all of the data that the company needs to back up.
+ Determines backup frequency, such as when to execute an initial full backup and when to
do incremental backups.
+Lists all roles in charge of backup procedures, such as backup administrators and IT team
members.
-Regulations and compliance requirements that have an influence on the company, such as
GDPR, CCPA, PCI DSS, SOX, and HIPAA, should be mentioned in the information security
policy.
Step 1: Identify and define the problem or issue that necessitates the development of a policy.
-The business must also be aware of the goals of its policies and understand that they could
change in order to resolve a problem or issue.
-A policy's development could take several months. The process needs to be "driven" by
someone, or even a committee.
-Research, consultation, and policy drafting are all needed tasks. The coordinator should
prepare a schedule of the tasks that must be accomplished, by whom, and when.
-Read the policy documents on the subject from different organizations. Search the internet
for legal issues. Call a meeting with staff members and other industry experts.Survey
respondents or a subset of respondents, such as coaches.
-Read the management committee meeting minutes (if allowed). Check out more documents,
including yearly reports or reports from events. Read magazines and trade journals. Obtain
legal counsel.
-The distribution of the discussion paper to all stakeholders is one of the initial phases in the
consultation process (interested parties). It may also be necessary to contact and alert
stakeholders in order to remind them to read the discussion material. Then, obtain as much
feedback as possible from all relevant stakeholders. This may be done through seminars,
public meetings, your website, and one-on-one interactions. Several months may be required
to ensure that this round of engagement is thorough.
-Once the consultation processes have concluded, the next step is to develop a draft policy.
-When finished, the draft policy should be distributed to important parties, advertised on the
organization's website and newsletter, and discussed at upcoming forums and meetings. It is
crucial to enlist the assistance of stakeholders before publishing the policy in order to
improve the language, clarify key terms, and make required changes.
Step 9: Adoption.
-When the policy development process coordinator is reasonably comfortable that all issues
and concerns regarding the policy have been addressed, it is time to finalize the policy. The
final policy statement must be formally accepted by the organization's management
(management committee), with an appropriate record kept in the minutes.
-The policy should be widely advertised to all company stakeholders after being formally
accepted. It could be necessary to hold training sessions to guarantee that every employee of
the firm is knowledgeable about and competent in using the policy. The policy could fail if
it is not properly stated.
P8 List the main components of an organisational disaster recovery plan, justifying the
reasons for inclusion.
-When downtime is intolerable, business continuity is essential. The plan should enable the
organization to operate at its most basic level during a crisis. By enabling an organization to
react promptly to an interruption, business continuity increases a company's resilience.
Strong business continuity protects the organization's reputation while saving money and
time. A protracted outage is risky for your finances, reputation, and personal safety.
Continuity of business operations may also be necessary for legal or regulatory reasons.
Knowing which laws apply to a particular organization is essential, especially in an era of
expanding regulation.
8.2 List the components of recovery plan.
A. Disaster Recovery Plan (DRP)
- A DRP is a written document that details the process for restoring IT resources following
an event that causes a significant disruption in service. A business continuity strategy must
include a disaster recovery plan (DRP) (BCP). It speaks of the organizational components
that depend on an effective IT infrastructure. In order to continue operating in the wake of
an event, even at a minimal level, a DRP works to help an organization resolve data loss and
recover system functionality.
- Since the risks associated with disasters and emergencies are constantly evolving, disaster
recovery planning is a continuous process. The company should regularly test the DRP to
determine the effectiveness and suitability of the procedures indicated in the plan. To take
into account modifications to business procedures, advancements in technology, and rising
catastrophic risks, the recovery team should regularly update the DRP.
- Recovery time objectives (RTO) and recovery point objectives (RPO) should be used to
categorize recovery objectives (RPO). RTO is the potential downtime before asset recovery,
whereas RPO is the amount of data you are willing to lose. Your disaster recovery strategy
should have these objectives established early on so that the right configuration may be
chosen. Discuss the ramifications of the prospective interruption with your company's top
management and operational staff for as little as one minute, up to one day, or even longer.
You can use this information to determine your RTO, RPO, and how frequently your data
needs to be backed up.
- You need to assess your assets contextually after taking an inventory of them. How does
your organization utilize these resources? Which assets would be most affected by a disaster
if they were damaged or lost? Sort all of your mapped assets from high to low effect by going
through each one.
-Not all of your data can always be backed up. It will be possible for you to decide which
assets should be prioritized in your disaster recovery strategy after you have an
understanding of the importance of each asset and how they relate to one another.
E. Propose A Budget.
- All firms, regardless of their resources, should have a disaster recovery strategy.While
highlighting the necessity of catastrophe recovery, senior management should also be shown
a variety of options at various price ranges. A disaster recovery plan with improved RTOs
and RPOs, more generous support for more vital services, and maybe inclusion in a larger
business continuity strategy are all included in higher budgets. With the right information,
management can evaluate risk and investment in disaster recovery plan technologies to strike
the right balance. Each company's disaster recovery plan requirements will be different.
8.3 Write down all the steps required in disaster recovery process.
• Step 1: Identify
- Inventory and map the location of all of your company's IT assets. Keep an eye out for
and specify dependents as you go. Determine which IT-related business operations are
crucial to being operational, since they will be the first to be considered when developing
your plan.
- This step must be completed carefully because it will affect the rest of the planning
process. Each of the important business functions you defined in step one will receive
recovery time objectives (RTOs) and recovery point objectives (RPOs) in step two.
• Step 2: Assess
- Assign a tier to each of the IT business processes that were identified in step one. The
highest-value applications and systems fall under the Tier 1 category. Tier 3 processes
would have the lowest priorities, followed by Tier 2 processes, which would be of
medium priority.
-Next, assign the proper recovery point goal (RPO) and recovery time objective (RTO)
to each tier's elements (RTO). Determine the actual cost of downtime for each of your
processes and systems. By doing so, you may better organize your priorities and
hopefully get the backing of management for a disaster recovery plan.
• Step 3: Customize
- After considering dependencies, layers, and the previously described RPOs and RTOs,
decide how certain business functions will be restored in the event of an interruption. The
third step of the process is the most challenging and time-consuming. However, you need
to have a well defined plan that can be implemented to ensure the continuity of your
important systems after a crisis (to the letter). This suggests that everything, including
floor plans, utility diagrams, system settings, and any other relevant information, should
be inventoried and mapped. Be sure to thoroughly test the user plan because it is unique.
After a tragedy, you don't want to realize that one of the key elements of your plan was
missing.
• Step 4: Blend
- For the most important workloads, supplement secure, cloud-based backup with on-
premises backup. There is no such thing as a one-size-fits-all solution to catastrophe
recovery; anyone who claims differently should be avoided. Because your organization's
demands are unique, a hybrid approach is most likely the best option.
- Furthermore, E2 and services that use comparable equipment provide you with the
added benefit of redundant backup. When it comes to your disaster recovery strategy, you
can never be too cautious.
• Step 5: Repeat
- Any catastrophe recovery strategy must include testing and adapting. not only during
the initial stages of planning. As your business and systems grow, so will your disaster
recovery needs. For organizations of any size, conditions and objectives are constantly
shifting, and your DR strategy will only be effective if it is regularly updated to reflect
changes.
- According to a recent poll of IT professionals, just 40% of businesses evaluate their
disaster recovery strategies on a yearly basis. Surprisingly, another 28% test their
strategies relatively infrequently, if at all.
8.4 Explain some of the policies and procedures that are required for business continuity.
A. Risk Assessment.
- Each department will identify, appraise, and rate potential dangers throughout the risk
assessment process. The Director of Emergency Preparedness will review the hazards.
This will result in a variety of consequences that may need extensive business impact
analysis (BIA) and recovery methods.
- The RTO created during the business impact analysis prioritizes recovery plans, which
are alternative ways to return business operations to a minimally acceptable level
following a business disruption. Recovery plans need a range of resources, including
personnel, infrastructure, tools, supplies, and IT. Each department must do an analysis of
the resources needed to carry out recovery measures in order to find any gaps.
- When the BCP is finished, the director of emergency preparation will train and test
everyone in the department to make sure they are all familiar with it. A continuity
planning committee made up of those involved before, during, and after a catastrophe or
significant interruption will be established by the director of emergency planning. Each
department will modify the BCP as necessary after training or actual situations.
• Regular Review and Upkeep
• Exercises and training
- Analysis of Business Impact (BIA). The business impact analysis (BIA) is the process
of determining, analyzing, and evaluating the possible impacts of an interruption or
suspension of important company activities, functions, and processes due to an accident,
emergency, or disaster. It is a methodical approach of estimating the possible and likely
repercussions of these disturbances, generally from the perspective of the worst-case
scenario.
Conclusion
In my most recent project, I discovered how to define security risks and carry out risk
analyses. Explain the risk assessment process, define assets, risks, and threat identification
techniques, and list the procedures for risk identification. I also learnt how to define data
protection, describe how data protection works in organizations, and explain the need for
data protection and security laws.
Finally, describe why business continuity is important. List the elements of the recovery
plan, make a list of all the steps required for disaster recovery, and mention some of the
policies and procedures crucial for business continuity.
References
[1] Learning Center. (n.d.). What is Data Protection | Principles, Strategies & Policies |
Imperva. [online] Available at: https://www.imperva.com/learn/data-security/data-
protection/#:~:text=Data%20protection%20is%20the%20process [Accessed 27 Dec. 2022].
[2] Grimmick, R. (2022). What is a Security Policy? Definition, Elements, and Examples.
[online] www.varonis.com. Available at: https://www.varonis.com/blog/what-is-a-security-
policy.