3.2. Identifying and analyzing the security
threats to, and vulnerabilities of the assets of
CRM systems within the organization.
The object of this step is to identify and assess the
risks to which the CRM systems and its assets are
exposed, in order to identify and select appropriate and
justified security safeguard. The likelihood occurred
threats lead to the potential adverse business impacts.
3.3. Implementing CRM security plan
The CRM security plan is a co-ordination document
defining the actions to be undertaken to implement the
required safeguards for a CRM system. This plan should
contain the results of the review described above, the
actions to be undertaken within short, medium and long
time frames to achieve and maintain the appropriate
security level, the costs, and an implementation
schedule.
For the implementation of safeguards, all the
necessary steps are described in the CRM security plan
should be carried out. The responsible person for the
plan (which normally is the CRM system security
officer) should ensure that the priorities and the
schedule outlined in the CRM security plan are
followed 3.4. Developing and implementing CRM
security awareness and training program.
The objective of the security awareness program is to
increase the level of awareness within the organization
to the point where security becomes second nature and
the process becomes a routine that all employees can
easily follow.
Besides the general security awareness program,
which should apply to everybody within an
organization, specific security training is required for
personnel with tasks and responsibilities related to CRM
security. The degree of depth of security training should
be depended on the overall importance CRM security
has for the organization, and should vary according to
the security requirements of the performed roles.
3.5. Following up the CRM security plan:
Follow-up, even though often neglected, is one of the
most important aspects of CRM security. The results of
follow-up actions are such as security compliance
checking of implemented safeguards, monitoring and
reviewing CRM security in day-to-day use, and reports
of security relevant incidents. The implemented
safeguards can only work effectively if they are checked
in real business life. It must be assured that they are
used correctly, and that any security incidents and
changes are detected and dealt with:
3.5.1 Following up the CRM Incident Handling and
disaster recovery. To identify the risks and to measure
their severity it has been emphasized that risk analysis is
required. To support risk analysis and enhance the
results, information is required on security incidents.
This information has to be gathered and analyzed in a
secure way, and be seen to provide benefit. Thus it is
important that any organization has a properly
constructed and organized CRM Incident Analysis
Scheme (CRM-IAS) in operation, and that the
information received and processed should be available
to support risk analysis and management and other
security related activities.
3.5.2 Following up the CRM security monitoring and
maintenance. Monitoring is an ongoing activity which
checks the system, its users, and the environment
maintain the level of security as laid out by the CRM
security plan. A plan for day to day monitoring should
be prepared to provide additional guidance and
procedures for ensuring ongoing secure operation.
3.5.3 Following up the CRM security change
management. CRM systems and the environment in
which they operate are constantly changing. These
changes are a result of the availability of new features and services, or the discovery of new threats and
vulnerabilities. These changes can also result in new
threats and vulnerabilities. Change of the CRM system
includes:
x New procedures
x New customer behavior and needs
x New features
x Software updates
x New CRM technology
x New users to include external groups or anonymous
groups, and
x Additional networking and interconnection.
When a change to a CRM system occurs or is
planned, it is important to determine what, if any,
impact the change will have on the security of the
system. If the system has a configuration control board
or other organizational structure to manage technical
system changes, the CRM system security officer, or
his/her representative, should be assigned to the board
and be given responsibility to make determinations
about whether any change will impact security, and if so
how
3.5.4 Following up the CRM-SMS Compliance.
Security compliance checking is the review and
analysis of the implemented safeguards. It is used
to check CRM systems or services to the security
requirements documented in the CRM systems or
services conform to the security requirements
documented in the CRM system security policy
and CRM system security plan.
The head of each agency is responsible for
compliance with and enforcement of this Policy.
Agency Chief Information Officers (CIO) shall
develop and implement an Agency CRM Security
Program to implement this policy and these
standards. The Security Program shall include a
timetable and controls for compliance. The
controls shall include the following items but are
not limited to these ones:
x Maintaining the confidentiality, integrity,
availability, and accountability of all States of CRM
applications and services.
x Protecting information according to its sensitivity,
criticality and value, regardless of the media on
which it is stored or automated systems that process
it, or the methods by which it is distributed
x Ensuring that risks to information security are
identified and also controls these risks.
x Implementing processes to ensure that all security
services meet the minimum requirements set force
in this policy and the attached standards. x Ensuring that all employees and contractors
understand and comply with this Policy, as well as
all applicable laws and regulations
x Implementing physical security controls to prevent
unauthorized and/or illegal access, misuse,
destruction or theft of the State s CRM assets
According to above statements, important parts of the
CRM-SMS are the assessment of risks, and how they
can be reduced to an acceptable level. After assessing
the security requirements of the CRM systems and
services, it is advisable to select a corporate risk analysis
strategy. Following the risk assessment, appropriate
safeguards are identified for each CRM system to
reduce the risks to an acceptable level. These safeguards
are implemented as outlined training program, which is
important for the effectiveness of the safeguards.
4. Risk management in CRM
Any organization that wants to enhance security
should put in place a strategy for risk management that
is suitable for its environment (customers and
organization,), and contains the means to address the
risks in effective manner. A required strategy focuses on
security effort where it is necessary and enables a cost
and time effective approach [21, 5].
If an organization decides to do nothing about CRM
security, or to postpone the implementation of
safeguards, management should be aware of the possible
implications of this decision, by risk assessment report.
This risk assessment during the acquisition planning
phase is a critical step. It is used to determine what types
of controls will be cost effective and will form the basis
for determining mandatory and desirable specifications.
The analysis, like other risk analyses, should consider
assets, threats to the assets, potential vulnerabilities, and
what can be done to reduce risks. This risk assessment
should take into consideration existing controls and their
effectiveness. This risk assessment will require
participation by the other functional groups. This risk
assessment will use input from the analysis of integrity,
availability, and confidentiality requirements as the
basis for determining the value of customers and market
information assets and the impact of security failures.
The selection of appropriate types of safeguards should
take into consideration the results of the level of
assurance analysis [12, 13, and 14].
Risk management has been affected on CRM life
cycle. Threats and vulnerabilities of CRM system data
is completely recognized and solved by suggested
method. At last briefly suggested method which has
following eight steps is proposed [2, 6, 10, 15, and 16]: