< Return to Video

Protection Of Information Assets | CISA Training Videos

  • 0:01 - 0:03
    Hello and welcome to the fifth domain of
  • 0:03 - 0:05
    the Certified Information Systems
  • 0:05 - 0:08
    Auditor, CISA, course offered by Simplilearn.
  • 0:09 - 0:11
    This domain will cover protection
  • 0:11 - 0:14
    of information assets. Let us look at the
  • 0:14 - 0:16
    objectives of this domain in the next
  • 0:16 - 0:19
    screen. By the end of this domain, you
  • 0:19 - 0:22
    should be able to understand and provide
  • 0:22 - 0:25
    assurance that the enterprise's security
  • 0:25 - 0:27
    policies, standards, procedures, and
  • 0:27 - 0:30
    controls ensure the confidentiality,
  • 0:30 - 0:32
    integrity, and availability of
  • 0:32 - 0:36
    information assets, detail the design,
  • 0:36 - 0:38
    implementation, and monitoring of
  • 0:38 - 0:41
    security controls, discuss the risks
  • 0:41 - 0:43
    associated with use of mobile and
  • 0:43 - 0:45
    wireless devices,
  • 0:45 - 0:47
    understand encryption techniques
  • 0:47 - 0:50
    such as public key infrastructure and
  • 0:50 - 0:53
    risks related to data leakage,
  • 0:53 - 0:56
    detail network detection tools and techniques,
  • 0:56 - 0:59
    discuss how confidential information can
  • 0:59 - 1:01
    be stored, retrieved, transported, and
  • 1:01 - 1:04
    disposed. The following screen gives an
  • 1:04 - 1:08
    overview of this domain. An information
  • 1:08 - 1:11
    asset is a component related to
  • 1:11 - 1:12
    provision of accurate data or
  • 1:12 - 1:15
    information for decision-making purposes
  • 1:15 - 1:18
    by an entity. It is considered to hold
  • 1:18 - 1:21
    value to that particular organization
  • 1:21 - 1:23
    and should therefore be protected by
  • 1:23 - 1:27
    ensuring confidentiality, integrity, and
  • 1:27 - 1:30
    availability, CIA.
  • 1:30 - 1:32
    Examples of information assets are
  • 1:32 - 1:36
    information or data, computer application
  • 1:36 - 1:40
    systems, computers, personal computers, PCs,
  • 1:40 - 1:44
    laptops, PDAs, phones, networks, local area
  • 1:44 - 1:48
    network, LAN, wide area network, WAN,
  • 1:48 - 1:51
    wireless networks, Human Resources,
  • 1:51 - 1:54
    facilities, main distribution facilities,
  • 1:54 - 1:58
    MDFs, data centers, server room, and other
  • 1:58 - 2:00
    technologies such as database
  • 2:00 - 2:03
    technologies among others. Let us
  • 2:03 - 2:05
    continue with the overview in the
  • 2:05 - 2:08
    following screen. The risks to business
  • 2:08 - 2:11
    include financial loss, electronic fraud,
  • 2:11 - 2:15
    legal repercussions, privacy issues, loss
  • 2:15 - 2:17
    of credibility or competitive edge,
  • 2:17 - 2:21
    blackmail, industrial espionage, sabotage,
  • 2:21 - 2:21
    and breach of
  • 2:21 - 2:25
    confidentiality. Security failures can be
  • 2:25 - 2:28
    costly to business as more costs are
  • 2:28 - 2:30
    incurred to secure systems and prevent
  • 2:30 - 2:33
    further failure. Further more costs are
  • 2:33 - 2:35
    incurred from losses from the failure
  • 2:35 - 2:38
    itself and when recovering from such
  • 2:38 - 2:41
    losses. Let us now look at threats to
  • 2:41 - 2:44
    information assets in the next slide. The
  • 2:44 - 2:47
    threats to information assets include
  • 2:47 - 2:50
    hackers, crackers, phreackers, authorized or
  • 2:50 - 2:54
    unauthorized employees, IS personnel, end
  • 2:54 - 2:57
    users, former employees, interested or
  • 2:57 - 3:00
    educated outsiders, competitors, organized
  • 3:00 - 3:02
    criminals, part-time and
  • 3:02 - 3:04
    temporary personnel, vendors and
  • 3:04 - 3:06
    consultants, and finally accidental
  • 3:06 - 3:09
    ignorance. Let us begin with the first
  • 3:09 - 3:11
    topic in this domain in the following
  • 3:11 - 3:14
    screen. In this topic, we will learn about
  • 3:14 - 3:16
    the concepts under the first knowledge
  • 3:16 - 3:18
    statement KS 5.1
  • 3:19 - 3:21
    We will begin with design,
  • 3:21 - 3:23
    implementation, and monitoring of
  • 3:23 - 3:26
    security controls in the next screen.
  • 3:27 - 3:28
    The key knowledge statement is to
  • 3:28 - 3:31
    understand the techniques for the design,
  • 3:31 - 3:32
    implementation, and monitoring of
  • 3:32 - 3:35
    security controls, including security
  • 3:35 - 3:38
    awareness programs. Security needs to be
  • 3:38 - 3:41
    aligned with business objectives to
  • 3:41 - 3:44
    provide reasonable reduction in risk.
  • 3:44 - 3:47
    Security objectives may include the following:
  • 3:47 - 3:48
    ensure the continued
  • 3:48 - 3:51
    availability of information systems,
  • 3:51 - 3:53
    ensure the integrity of information
  • 3:53 - 3:56
    stored on its computer systems and
  • 3:56 - 3:58
    security while the information is in
  • 3:58 - 4:01
    transit, preserve the confidentiality of
  • 4:01 - 4:04
    sensitive data while stored and in
  • 4:04 - 4:06
    transit, ensure compliance with
  • 4:06 - 4:08
    applicable laws, regulations, and
  • 4:08 - 4:11
    standards. Let us continue discussing
  • 4:11 - 4:14
    design, implementation, and monitoring of
  • 4:14 - 4:16
    security controls in the next screen.
  • 4:17 - 4:19
    Ensure adherence to trust and
  • 4:19 - 4:21
    obligation requirements for any
  • 4:21 - 4:23
    information assets accordance with the
  • 4:23 - 4:26
    applicable privacy policy or privacy
  • 4:26 - 4:29
    laws and regulations. Prudence in
  • 4:29 - 4:31
    application of control is important
  • 4:31 - 4:34
    because controls entail a cost either
  • 4:34 - 4:36
    directly or indirectly by impacting on
  • 4:36 - 4:39
    business operations. The business impact
  • 4:39 - 4:43
    analysis, BIA, is the process used to
  • 4:43 - 4:45
    establish the material adverse events
  • 4:45 - 4:48
    the business should be worried about. The
  • 4:48 - 4:50
    following screen lists the main areas to
  • 4:50 - 4:52
    be covered under this knowledge statement.
  • 4:53 - 4:55
    The main areas to cover here
  • 4:55 - 4:58
    are key elements of information security
  • 4:58 - 5:01
    management, critical success factors to
  • 5:01 - 5:04
    information security, inventory and
  • 5:04 - 5:07
    classifications of information assets,
  • 5:07 - 5:11
    network infrastructure security. In the
  • 5:11 - 5:12
    next screen, we will learn about
  • 5:12 - 5:15
    information security management.
  • 5:15 - 5:18
    Effective ISM is the most
  • 5:18 - 5:20
    critical factor in protecting
  • 5:20 - 5:23
    information assets and privacy. The
  • 5:23 - 5:25
    factors that raise the profile of
  • 5:25 - 5:28
    information and privacy risk include
  • 5:28 - 5:30
    electronic trading through service
  • 5:30 - 5:33
    providers and directly with customers,
  • 5:33 - 5:35
    loss of organizational barriers through
  • 5:35 - 5:38
    use of remote access facilities, and high
  • 5:38 - 5:41
    profile security exposures: viruses,
  • 5:41 - 5:45
    denial of service, DOS, attacks, intrusions,
  • 5:45 - 5:48
    unauthorized access, disclosures and
  • 5:48 - 5:52
    identity theft over the Internet, etc. Let
  • 5:52 - 5:54
    us continue discussing information
  • 5:54 - 5:57
    security management, ISM, in the next screen.
  • 5:58 - 6:00
    Security awareness and education
  • 6:00 - 6:03
    through training and regular updates:
  • 6:03 - 6:05
    written policies and procedures and
  • 6:05 - 6:08
    updates, non-disclosure statements signed
  • 6:08 - 6:10
    by employees,
  • 6:10 - 6:13
    newsletters, web pages, videos,
  • 6:13 - 6:16
    and other media, visible enforcement of
  • 6:16 - 6:19
    security rules, simulated security
  • 6:19 - 6:23
    incidents and simulated drills, rewards
  • 6:23 - 6:26
    for reporting suspicious events, periodic
  • 6:26 - 6:30
    audits. Monitoring and compliance: control
  • 6:30 - 6:32
    includes an element of monitoring and
  • 6:32 - 6:35
    usually relates to regulatory, legal
  • 6:35 - 6:39
    compliance, incident handling and response
  • 6:40 - 6:41
    In the next few screens, we will
  • 6:41 - 6:44
    learn about roles and responsibilities
  • 6:44 - 6:45
    under the information security
  • 6:45 - 6:49
    management. The security objectives to
  • 6:49 - 6:52
    meet business requirements are to ensure
  • 6:52 - 6:54
    continued availability of information
  • 6:54 - 6:56
    systems, to ensure integrity of
  • 6:56 - 6:59
    information stored in systems and while
  • 6:59 - 7:00
    in transit,
  • 7:00 - 7:03
    to preserve confidentiality of sensitive
  • 7:03 - 7:07
    data, to ensure conformity to applicable
  • 7:07 - 7:10
    laws, regulations, and standards, to ensure
  • 7:10 - 7:12
    adherence to trust and obligation
  • 7:12 - 7:15
    requirements, to ensure protection of
  • 7:15 - 7:18
    sensitive data. Data integrity, as it
  • 7:18 - 7:21
    relates to security objectives, generally
  • 7:21 - 7:24
    refers to accuracy, completeness,
  • 7:24 - 7:27
    consistency or neutrality, validity, and
  • 7:27 - 7:29
    verifiability of the data once loaded on
  • 7:29 - 7:32
    the system. Integrity refers to
  • 7:32 - 7:35
    reliability of data. Let us continue
  • 7:35 - 7:37
    discussing information security
  • 7:37 - 7:40
    management, ISM, in the next screen.
  • 7:41 - 7:42
    The key elements of
  • 7:42 - 7:46
    ISM. Senior management commitment and
  • 7:46 - 7:48
    support, the risk management begins at
  • 7:48 - 7:52
    the top. Policies and procedures, the
  • 7:52 - 7:54
    framework that captures top management
  • 7:54 - 7:58
    declaration of direction. Organization,
  • 7:58 - 8:00
    clearly defined and allocated roles and
  • 8:00 - 8:02
    responsibilities, supplemented with
  • 8:02 - 8:06
    guidance, usually relates to regulatory,
  • 8:06 - 8:08
    legal compliance. Let us continue
  • 8:08 - 8:10
    discussing information security
  • 8:10 - 8:14
    management, ISM, in the next screen.
  • 8:14 - 8:17
    Roles and responsibilities must be defined,
  • 8:17 - 8:20
    documented, and communicated to personnel
  • 8:20 - 8:23
    and management. IS security steering
  • 8:23 - 8:26
    committee is represented by individuals
  • 8:26 - 8:29
    from various management levels. It also
  • 8:29 - 8:32
    discusses and approves security policies
  • 8:32 - 8:35
    guidelines and procedures; with input
  • 8:35 - 8:38
    from end users, executive management,
  • 8:38 - 8:41
    auditors, security administration, IS
  • 8:41 - 8:44
    personnel, and legal counsel. The
  • 8:44 - 8:46
    committee is formally established with
  • 8:46 - 8:49
    appropriate Terms of Reference. Executive
  • 8:49 - 8:52
    management responsible for the overall
  • 8:52 - 8:54
    protection of information assets and
  • 8:54 - 8:58
    issuing and maintaining the policy framework.
  • 8:58 - 9:00
    Security advisory group is
  • 9:00 - 9:03
    responsible for defining information
  • 9:03 - 9:05
    risk management process and acceptable
  • 9:05 - 9:08
    level of risk and reviewing security
  • 9:08 - 9:11
    plans. It is comprised of people involved
  • 9:11 - 9:13
    in the business and provides comments on
  • 9:13 - 9:15
    security issues to chief security
  • 9:15 - 9:19
    officer, CSO. It also advises the business
  • 9:19 - 9:21
    whether the security programs meet
  • 9:21 - 9:23
    business objectives.
  • 9:24 - 9:26
    Chief information security
  • 9:26 - 9:26
    officer,
  • 9:26 - 9:29
    CISO, is a senior level corporate
  • 9:29 - 9:32
    official responsible for articulating
  • 9:32 - 9:34
    and enforcing policies used to protect
  • 9:34 - 9:37
    information assets. He has a much broader
  • 9:37 - 9:40
    role than CSO who is normally only
  • 9:40 - 9:43
    responsible for physical security within
  • 9:43 - 9:44
    the organization.
  • 9:44 - 9:46
    Information asset owners
  • 9:46 - 9:48
    and data owners are entrusted with the
  • 9:48 - 9:51
    responsibility for the owned asset,
  • 9:51 - 9:52
    including performance of a risk
  • 9:52 - 9:54
    assessment, selection of appropriate
  • 9:54 - 9:57
    controls to mitigate the risk and to
  • 9:57 - 10:00
    accept the residual risk.
  • 10:00 - 10:02
    Process owners ensure appropriate
  • 10:02 - 10:04
    security measures consistent with
  • 10:04 - 10:07
    organizational policy are maintained.
  • 10:07 - 10:09
    Users comply with procedures
  • 10:09 - 10:12
    set out in the security policy, and
  • 10:12 - 10:14
    adhere to privacy and security
  • 10:14 - 10:17
    regulations, often specific to sensitive
  • 10:17 - 10:20
    data, for example, health, legal, finance,
  • 10:20 - 10:25
    etc. Chief privacy officer, CPO, is a
  • 10:25 - 10:27
    senior level corporate official and is
  • 10:27 - 10:29
    responsible for articulating and
  • 10:29 - 10:32
    enforcing policies used to protect
  • 10:32 - 10:36
    customers' and employees' privacy rights.
  • 10:36 - 10:38
    External parties follow procedures set
  • 10:38 - 10:41
    out in the security policy. They adhere
  • 10:41 - 10:43
    to privacy and security regulations
  • 10:43 - 10:45
    often specific to sensitive data, for
  • 10:45 - 10:49
    example, health, legal, finance, etc.
  • 10:49 - 10:52
    Information security administrator is a
  • 10:52 - 10:55
    staff level position. He is responsible
  • 10:55 - 10:57
    for providing adequate physical and
  • 10:57 - 11:00
    logical security for IS programs, data
  • 11:00 - 11:02
    and equipment, normally guided by the
  • 11:02 - 11:05
    information security policies.
  • 11:05 - 11:07
    Security specialists and
  • 11:07 - 11:09
    advisors assist with the design,
  • 11:09 - 11:11
    implementation, management, and review of
  • 11:11 - 11:14
    security policies, standards, and
  • 11:14 - 11:17
    procedures. IT developers implements
  • 11:17 - 11:19
    information security within their
  • 11:19 - 11:22
    applications. IS auditors provide
  • 11:22 - 11:25
    independent assurance on appropriateness
  • 11:25 - 11:27
    and effectiveness of information
  • 11:27 - 11:30
    security objectives and controls related
  • 11:30 - 11:32
    to these objectives. In the next screen,
  • 11:32 - 11:34
    we will learn about system access
  • 11:34 - 11:38
    permissions. System access permission is
  • 11:38 - 11:40
    the ability to do something with a
  • 11:40 - 11:43
    computer resource. Read, create, modify, or
  • 11:43 - 11:47
    delete a file or data, execute a program
  • 11:47 - 11:49
    or use an external connection. It is
  • 11:49 - 11:52
    controlled at the physical and or logical
  • 11:52 - 11:55
    level. Logical controls govern access to
  • 11:55 - 11:58
    information and programs. It is built
  • 11:58 - 12:00
    into operating systems
  • 12:00 - 12:03
    invoked through access control software,
  • 12:03 - 12:06
    and incorporated in application programs,
  • 12:06 - 12:09
    DBs, network control devices, and
  • 12:09 - 12:12
    utilities. Let us continue discussing
  • 12:12 - 12:14
    system access permissions in the next
  • 12:14 - 12:18
    screen. Physical controls restrict entry
  • 12:18 - 12:21
    and exit of personnel, movement of
  • 12:21 - 12:24
    equipment and media. They include badges,
  • 12:24 - 12:25
    memory cards, keys, and
  • 12:25 - 12:29
    biometrics. Access is granted on a
  • 12:29 - 12:31
    documented, need-to-know basis with
  • 12:31 - 12:34
    legitimate business requirement based on
  • 12:34 - 12:36
    least privilege and on segregation of
  • 12:36 - 12:37
    duties principles.
  • 12:38 - 12:40
    Access principles relate to
  • 12:40 - 12:43
    four layers of security. Namely network,
  • 12:43 - 12:46
    platform, typically the operating system,
  • 12:46 - 12:50
    database, and application. In the next
  • 12:50 - 12:52
    screen, we will learn about mandatory and
  • 12:52 - 12:53
    discretionary access
  • 12:53 - 12:58
    controls. The mandatory access controls,
  • 12:58 - 13:02
    MACs, are logical access controls, MACs,
  • 13:02 - 13:04
    that cannot be modified by normal users
  • 13:04 - 13:08
    or data owners. They act by default and
  • 13:08 - 13:10
    are used to enforce critical security
  • 13:10 - 13:13
    without possible exception. Only
  • 13:13 - 13:15
    administrators can grant a right of
  • 13:15 - 13:18
    access guided by an established policy
  • 13:18 - 13:18
    of the
  • 13:18 - 13:21
    organization. Discretionary access
  • 13:21 - 13:24
    controls, DACs, controls may be
  • 13:24 - 13:27
    configured or modified by the users or
  • 13:27 - 13:30
    data owners. Access may be activated or
  • 13:30 - 13:34
    modified by a data owner. DACs cannot
  • 13:34 - 13:36
    override MACs, and they act as
  • 13:36 - 13:39
    additional filters to restrict access
  • 13:39 - 13:41
    further. In the next few screens, we will
  • 13:41 - 13:44
    learn about privacy management issues
  • 13:44 - 13:46
    and role of IS auditors.
  • 13:47 - 13:48
    Privacy issues relates to
  • 13:48 - 13:51
    personally identifiable information, for
  • 13:51 - 13:53
    example, personal identification number,
  • 13:53 - 13:57
    PIN. Regulations generally restrict use
  • 13:57 - 13:59
    of such data by giving the subject individual
  • 13:59 - 14:01
    rights to access and correct that
  • 14:01 - 14:05
    data. It also governs how such data is
  • 14:05 - 14:07
    obtained, requiring knowledge and consent
  • 14:07 - 14:10
    of the data subject. Impact of risks
  • 14:10 - 14:13
    including marketing risks, transported
  • 14:13 - 14:16
    data flow and variations in regulations,
  • 14:16 - 14:18
    and may require privacy experts during
  • 14:18 - 14:19
    risk assessment.
  • 14:20 - 14:22
    The goals of a privacy impact
  • 14:22 - 14:25
    assessment are identifying the nature of
  • 14:25 - 14:28
    personally identifiable information
  • 14:28 - 14:29
    relating to business
  • 14:29 - 14:33
    processes. Documenting the collection, use,
  • 14:33 - 14:36
    disclosure, storage, and destruction of
  • 14:36 - 14:39
    personally identifiable information.
  • 14:39 - 14:40
    Providing management with an
  • 14:40 - 14:42
    understanding of privacy risk and
  • 14:42 - 14:45
    options to mitigate this risk. Ensuring
  • 14:45 - 14:47
    accountability for privacy. And
  • 14:47 - 14:51
    facilitating compliance with relevant regulations.
  • 14:52 - 14:54
    IS audit considerations
  • 14:54 - 14:56
    relating to privacy include adequacy of
  • 14:56 - 14:58
    privacy assessment, for example,
  • 14:58 - 15:01
    compliance with with privacy policy, laws,
  • 15:01 - 15:03
    and other regulations, and the manner in
  • 15:03 - 15:06
    which IT is used for competitive gain.
  • 15:06 - 15:08
    Another consideration is the ongoing
  • 15:08 - 15:11
    assessments conducted when new products
  • 15:11 - 15:13
    services, systems, operations, processes,
  • 15:13 - 15:15
    and third parties are under
  • 15:15 - 15:18
    consideration. Besides transborder and
  • 15:18 - 15:21
    multinational laws should also be considered.
  • 15:22 - 15:23
    Focus and extent of privacy
  • 15:23 - 15:26
    impact assessment may depend on changes
  • 15:26 - 15:29
    in technology, processes, or people as
  • 15:29 - 15:31
    shown by below. In the next few screens,
  • 15:31 - 15:34
    we will learn about information security
  • 15:34 - 15:37
    and external parties. Human Resources
  • 15:37 - 15:40
    security and third parties. Security
  • 15:40 - 15:42
    roles and responsibilities of employees,
  • 15:42 - 15:45
    contractors, and third-party users should
  • 15:45 - 15:47
    be defined and documented in accordance
  • 15:47 - 15:50
    with the organizational security policy.
  • 15:50 - 15:52
    Information security policies to guide
  • 15:52 - 15:54
    employees, contractors, and third-party
  • 15:54 - 15:58
    users. Information security and external
  • 15:58 - 16:00
    parties. Security of information and
  • 16:00 - 16:03
    processing facilities must be maintained
  • 16:03 - 16:06
    when external party services or products
  • 16:06 - 16:08
    are introduced. Controls must be agreed
  • 16:08 - 16:11
    to and defined in a formal agreement.
  • 16:11 - 16:13
    Organization must have right to audit
  • 16:13 - 16:15
    the implementation and operations.
  • 16:16 - 16:18
    The external party arrangements
  • 16:18 - 16:21
    include service providers, ISPs, network
  • 16:21 - 16:25
    providers, managed security services,
  • 16:25 - 16:27
    customers, outsourcing facilities and or
  • 16:27 - 16:30
    operations, IT systems, data
  • 16:30 - 16:32
    collection services, management and
  • 16:32 - 16:34
    business consultants and auditors,
  • 16:34 - 16:36
    developers and suppliers, cleaning,
  • 16:36 - 16:39
    catering, and other outsourced support
  • 16:39 - 16:41
    services. Others include temporary
  • 16:41 - 16:44
    personnel, student placement, and other
  • 16:44 - 16:46
    casual short-term appointments.
  • 16:47 - 16:48
    The risks related to
  • 16:48 - 16:51
    external party access is information
  • 16:51 - 16:52
    processing facilities required to be
  • 16:52 - 16:56
    accessed by external parties. These types
  • 16:56 - 16:59
    of access include physical access, logical
  • 16:59 - 17:03
    access, network connectivity, organization
  • 17:03 - 17:06
    and external party, value and sensitivity
  • 17:06 - 17:08
    of information involved, and its
  • 17:08 - 17:10
    criticality for business operations, and
  • 17:10 - 17:13
    legal and other regulatory requirements.
  • 17:14 - 17:16
    Security in relation to
  • 17:16 - 17:18
    customers involve identifying security
  • 17:18 - 17:21
    requirements for customers access. The
  • 17:21 - 17:22
    customer access security
  • 17:22 - 17:25
    considerations: asset protection,
  • 17:25 - 17:28
    description of product or service to be
  • 17:28 - 17:30
    provided, reasons, requirements, and
  • 17:30 - 17:33
    benefits for customer access, access
  • 17:33 - 17:36
    control policy, arrangements for
  • 17:36 - 17:38
    reporting, notification, and investigation
  • 17:38 - 17:39
    of information
  • 17:39 - 17:42
    inaccuracies, target levels of service
  • 17:42 - 17:45
    and unacceptable levels of service, right
  • 17:45 - 17:48
    to monitor and revoke any activity
  • 17:48 - 17:50
    related to an organization's assets,
  • 17:50 - 17:52
    intellectual property rights and
  • 17:52 - 17:55
    copyright assignment. You will now
  • 17:55 - 17:57
    attempt a question to test what you have
  • 17:57 - 17:59
    learned so far. In this topic, we will
  • 17:59 - 18:01
    learn about the concepts in Knowledge
  • 18:01 - 18:03
    Statement 5.2.
  • 18:03 - 18:05
    Let us discuss monitoring and
  • 18:05 - 18:08
    responding to security incidents in the
  • 18:08 - 18:10
    following screens. The key knowledge
  • 18:10 - 18:12
    point is the processes related to
  • 18:12 - 18:15
    monitoring and responding to security
  • 18:15 - 18:17
    incidents, for example, escalation
  • 18:17 - 18:20
    procedures, emergency incident response
  • 18:20 - 18:23
    team. A formal incident response
  • 18:23 - 18:25
    capability should be established to
  • 18:25 - 18:27
    minimize the impact of security
  • 18:27 - 18:29
    incidents recovery in a timely and
  • 18:29 - 18:32
    controlled manner and learn from such
  • 18:32 - 18:34
    incidents. History should be kept through
  • 18:34 - 18:37
    properly recording of incidents. While
  • 18:37 - 18:39
    security management may be responsible
  • 18:39 - 18:42
    for monitoring and investigating events
  • 18:42 - 18:44
    and may have drafted or set a
  • 18:44 - 18:47
    requirement for escalation procedures,
  • 18:47 - 18:49
    other functions must be involved to
  • 18:49 - 18:52
    ensure proper response. These functions
  • 18:52 - 18:54
    must have well-defined and communicated
  • 18:54 - 18:56
    processes in place that are tested
  • 18:56 - 18:59
    periodically. The main areas covered here
  • 18:59 - 19:03
    are security incident handling and response.
  • 19:04 - 19:05
    In the next screen, we will
  • 19:05 - 19:09
    discuss about incident handling and response.
  • 19:09 - 19:12
    An incident is an adverse event
  • 19:12 - 19:14
    that threatens some aspect of
  • 19:14 - 19:17
    information security. To minimize damage
  • 19:17 - 19:20
    from security incidents and to recover
  • 19:20 - 19:22
    and to learn from such incidents, a
  • 19:22 - 19:25
    formal incident response capability had
  • 19:25 - 19:27
    to be established, and it includes
  • 19:27 - 19:30
    planning and preparation, detection,
  • 19:30 - 19:33
    initiation, recording, evaluation,
  • 19:33 - 19:36
    containment, eradication, escalation,
  • 19:36 - 19:39
    response, recovery, closure, and post
  • 19:39 - 19:42
    incident review. Let us continue
  • 19:42 - 19:45
    discussing incident handling and response.
  • 19:46 - 19:47
    Procedures are defined for
  • 19:47 - 19:50
    reporting different types of incidents.
  • 19:50 - 19:52
    The process involves quick reporting and
  • 19:52 - 19:54
    collection of evidence, and formal
  • 19:54 - 19:56
    disciplinary process, and where
  • 19:56 - 19:59
    applicable, automated intrusion detection
  • 19:59 - 20:02
    systems. Incident handling and response
  • 20:02 - 20:04
    roles involve coordinator who is the
  • 20:04 - 20:07
    liaison to business process owners,
  • 20:07 - 20:10
    director who oversees incident response
  • 20:10 - 20:13
    capability, managers who manage
  • 20:13 - 20:15
    individual incidents, security
  • 20:15 - 20:18
    specialists that detect, investigate,
  • 20:18 - 20:21
    contain, and recover from incidents,
  • 20:21 - 20:23
    non-security technical specialists that
  • 20:23 - 20:25
    provide assistance on subject matter
  • 20:25 - 20:29
    expertise, business unit leader liaison
  • 20:29 - 20:32
    which include legal, HR, and PR. Logical
  • 20:32 - 20:35
    access controls is another area we're
  • 20:35 - 20:38
    going to learn in subsequent slides. You
  • 20:38 - 20:40
    will now attempt a question to test what
  • 20:40 - 20:42
    you have learned so far. In this topic, we
  • 20:42 - 20:44
    will learn about the concepts in
  • 20:44 - 20:46
    Knowledge Statement 5.3
  • 20:46 - 20:48
    Let us discuss logical access
  • 20:48 - 20:50
    controls in the following
  • 20:50 - 20:53
    screens. Knowledge point to learn here is
  • 20:53 - 20:55
    logical access controls for the
  • 20:55 - 20:58
    identification, authentication, and
  • 20:58 - 21:00
    restriction of users to authorized
  • 21:00 - 21:03
    functions and data. logical access
  • 21:03 - 21:05
    controls are used to manage and protect
  • 21:05 - 21:08
    information assets. Controls enact and
  • 21:08 - 21:10
    substantiate policies and procedures
  • 21:10 - 21:13
    designed by management to protect
  • 21:13 - 21:15
    information assets. Controls exist at
  • 21:15 - 21:18
    both the operating system level and the
  • 21:18 - 21:20
    application level, so it is important to
  • 21:20 - 21:23
    understand logical access controls as
  • 21:23 - 21:26
    they apply to systems that may reside on
  • 21:26 - 21:29
    multiple operating system platforms and
  • 21:29 - 21:31
    involve more than one application system
  • 21:31 - 21:34
    or authentication point. Let us continue
  • 21:34 - 21:37
    the discussion about logical access
  • 21:37 - 21:39
    controls in the next few screens.
  • 21:40 - 21:42
    Logical security is often
  • 21:42 - 21:44
    determined based on the job function of
  • 21:44 - 21:47
    users. The success of logical access
  • 21:47 - 21:50
    controls is tied to the strength of the
  • 21:50 - 21:53
    authentication method, for example, strong
  • 21:53 - 21:56
    passwords. All user access to systems and
  • 21:56 - 21:59
    data should be appropriately authorized
  • 21:59 - 22:01
    and should be commensurate it with the
  • 22:01 - 22:04
    role of the individual. Authorization
  • 22:04 - 22:07
    generally takes the form of signatures,
  • 22:07 - 22:09
    physical or electronic, a relevant
  • 22:09 - 22:11
    management. The strength of the
  • 22:11 - 22:13
    authentication is proportional to the
  • 22:13 - 22:16
    quality of the method used. Strong
  • 22:16 - 22:18
    authentication may include dual or
  • 22:18 - 22:22
    multiactor authentication using user 10,
  • 22:22 - 22:24
    password tokens, and
  • 22:24 - 22:27
    biometrics. The main areas covered here
  • 22:27 - 22:30
    are logical access.
  • 22:30 - 22:32
    Logical access controls are the primary
  • 22:32 - 22:34
    means used to manage and protect
  • 22:34 - 22:38
    information assets. These exposures can
  • 22:38 - 22:40
    result in minor inconveniences to a
  • 22:40 - 22:43
    total shutdown of computer functions.
  • 22:43 - 22:47
    Logical access controls involve managing
  • 22:47 - 22:49
    and controlling access to information
  • 22:49 - 22:52
    resources. It is based on management
  • 22:52 - 22:54
    policies and procedures for information
  • 22:54 - 22:58
    security. Logical access controls must be
  • 22:58 - 23:01
    evaluated vis-à-vis information security
  • 23:01 - 23:04
    objectives. Familiarization with the IT
  • 23:04 - 23:07
    environment helps in determining which
  • 23:07 - 23:10
    areas, from a risk standpoint, warrant IS
  • 23:10 - 23:12
    auditing attention. This includes
  • 23:12 - 23:15
    reviewing security layers associated
  • 23:15 - 23:20
    with IS architecture: network, OS, database, application.
  • 23:20 - 23:23
    Paths of logical access,
  • 23:23 - 23:26
    points of entry to IS infrastructure:
  • 23:26 - 23:29
    back-end, front-end systems, internally based
  • 23:29 - 23:32
    users, externally-based users, and direct
  • 23:32 - 23:35
    access to specific servers. All points of
  • 23:35 - 23:39
    entry must be known. General points of
  • 23:39 - 23:41
    entry relate to network or telecomm
  • 23:41 - 23:43
    infrastructure in controlling access to
  • 23:43 - 23:44
    information
  • 23:44 - 23:47
    resources. Typical client-server
  • 23:47 - 23:50
    environment: primary domain controllers
  • 23:50 - 23:52
    network management devices, for example,
  • 23:52 - 23:55
    routers and firewalls. General modes of
  • 23:55 - 23:58
    access: network connectivity, remote
  • 23:58 - 24:01
    access, remotely dialing into a network
  • 24:01 - 24:03
    for services that can be performed
  • 24:03 - 24:06
    remotely, for example, email.
  • 24:06 - 24:09
    Traditional points of entry. Mainly applicable for
  • 24:09 - 24:11
    mainframe-based systems used for large
  • 24:11 - 24:13
    database systems or "legacy"
  • 24:13 - 24:17
    applications. Operator console, these are
  • 24:17 - 24:19
    privileged computer terminals that
  • 24:19 - 24:21
    control most computer operations and
  • 24:21 - 24:23
    functions. They provide high level of
  • 24:23 - 24:26
    system access but do not have strong
  • 24:26 - 24:29
    logical access controls. It is located in
  • 24:29 - 24:32
    a suitably controlled facility so that
  • 24:32 - 24:34
    physical access can only be gained by
  • 24:34 - 24:35
    authorized
  • 24:35 - 24:38
    personnel. Online workstations in client-server
  • 24:38 - 24:41
    environments. This method
  • 24:41 - 24:43
    typically requires at least a logon ID
  • 24:43 - 24:46
    and password to gain access to the host
  • 24:46 - 24:48
    computer system. It may also require
  • 24:48 - 24:51
    further entry of authentication or
  • 24:51 - 24:53
    identification data for access to
  • 24:53 - 24:56
    application specific systems.
  • 24:56 - 24:59
    IS resources are more accessible and
  • 24:59 - 25:02
    available anytime and anywhere. Computers
  • 25:02 - 25:05
    store large volumes of data. Sharing of
  • 25:05 - 25:07
    resources has increased from one system
  • 25:07 - 25:10
    to another. And accessibility has
  • 25:10 - 25:13
    increased through intranet and internet.
  • 25:13 - 25:15
    Logical access control software has
  • 25:15 - 25:18
    become critical in protecting IS
  • 25:18 - 25:20
    resources. It prevents unauthorized
  • 25:20 - 25:23
    access and modification to sensitive
  • 25:23 - 25:26
    data, and use of critical functions. It is
  • 25:26 - 25:28
    applied across all layers of IS
  • 25:28 - 25:32
    architecture, network, OS, DBs, and applications.
  • 25:32 - 25:34
    Common attributes of this
  • 25:34 - 25:36
    software is that it has some form of
  • 25:36 - 25:38
    identification and
  • 25:38 - 25:40
    authentication, provides access
  • 25:40 - 25:43
    authorization. It also checks specific
  • 25:43 - 25:45
    information resource and provide logs
  • 25:45 - 25:47
    and reporting of user
  • 25:47 - 25:50
    activities. Greatest degree of protection
  • 25:50 - 25:52
    is applied at the network and platform
  • 25:52 - 25:55
    OS level mainly because it is the
  • 25:55 - 25:58
    primary point of entry to systems.
  • 25:58 - 26:01
    Besides it is the foundation, primary
  • 26:01 - 26:03
    infrastructure, on which applications and
  • 26:03 - 26:07
    DBs will reside. Also an OS system access
  • 26:07 - 26:09
    control software interfaces with
  • 26:09 - 26:12
    databases and or applications to protect
  • 26:12 - 26:16
    system libraries and datasets. These
  • 26:16 - 26:18
    network devices, for example, routers and
  • 26:18 - 26:21
    firewalls, manage external access to
  • 26:21 - 26:25
    networks, thus need the highest degree of protection.
  • 26:25 - 26:27
    General OS application access
  • 26:27 - 26:30
    control software functions include
  • 26:30 - 26:32
    creating or changing user profiles,
  • 26:32 - 26:34
    assigning user identification and
  • 26:34 - 26:37
    authentication, applying user logon
  • 26:37 - 26:40
    limitation rules, for example, restrict
  • 26:40 - 26:43
    logon IDs to specific workstations at
  • 26:43 - 26:46
    specific times, establishing rules for
  • 26:46 - 26:49
    access to specific resources, creating
  • 26:49 - 26:51
    individual accountability and
  • 26:51 - 26:54
    auditability by logging user activities,
  • 26:54 - 26:57
    logging events, and reporting capabilities.
  • 26:58 - 26:59
    Database or
  • 26:59 - 27:01
    application level controls creates or
  • 27:01 - 27:05
    changes data files and database profiles.
  • 27:05 - 27:08
    It also verifies user authorization at
  • 27:08 - 27:11
    the application and transaction level
  • 27:11 - 27:13
    within the application and at the field
  • 27:13 - 27:17
    level for changes within the database. It
  • 27:17 - 27:19
    also verifies subsystem authorization
  • 27:19 - 27:22
    for the user at the file level. In
  • 27:22 - 27:24
    addition, it logs database, data
  • 27:24 - 27:27
    communications access activities for
  • 27:27 - 27:30
    monitoring access by violations. You will
  • 27:30 - 27:32
    now attempt to question to test what you
  • 27:32 - 27:34
    have learned so far. In this topic, we
  • 27:34 - 27:36
    will learn about the concepts in
  • 27:36 - 27:38
    Knowledge Statement 5.4
  • 27:38 - 27:41
    Let us discuss security controls
  • 27:41 - 27:44
    related to hardware system software.
  • 27:44 - 27:47
    In this slide, we learn on the
  • 27:47 - 27:49
    security controls related to hardware,
  • 27:49 - 27:53
    system software, for example, applications,
  • 27:53 - 27:55
    operating systems, and database
  • 27:55 - 27:59
    management systems. Access control software
  • 27:59 - 28:01
    utilizes both identification and
  • 28:01 - 28:04
    authentication, I&A. Once
  • 28:04 - 28:06
    authenticated, the system then restricts
  • 28:06 - 28:10
    access based on the specific role of the user.
  • 28:11 - 28:13
    I&A is the process by which the
  • 28:13 - 28:17
    system obtains identity from a user, the
  • 28:17 - 28:19
    credentials needed to authenticate
  • 28:19 - 28:22
    identity, and validates both pieces of
  • 28:22 - 28:25
    information. I&A is a critical building
  • 28:25 - 28:28
    block of computer security since it is
  • 28:28 - 28:31
    needed for most types of access control
  • 28:31 - 28:34
    and is necessary for establishing user
  • 28:34 - 28:37
    accountability. For most systems, I&A is
  • 28:37 - 28:40
    the first line of defense because it
  • 28:40 - 28:42
    prevents unauthorized access or
  • 28:42 - 28:45
    unauthorized processes to a computer
  • 28:45 - 28:49
    system or an information asset. In the
  • 28:49 - 28:51
    next screen, we will discuss more about
  • 28:51 - 28:54
    security controls related to hardware
  • 28:54 - 28:58
    and system software. Logical access can
  • 28:58 - 29:01
    be implemented in various ways. The IS
  • 29:01 - 29:03
    auditor should be aware of the strengths
  • 29:03 - 29:06
    and weaknesses of various architectures
  • 29:06 - 29:09
    such as single sign-on, SSO, where a
  • 29:09 - 29:11
    single authentication will enable access
  • 29:11 - 29:14
    to all authorized applications, identity
  • 29:14 - 29:16
    management, multifactor
  • 29:16 - 29:19
    authentication. If this risk is
  • 29:19 - 29:21
    considered manageable, it should drive
  • 29:21 - 29:24
    the implementation of multiactor
  • 29:24 - 29:26
    authentication. The main areas covered
  • 29:26 - 29:28
    here are identification and
  • 29:28 - 29:32
    authentication, single sign-on. In the
  • 29:32 - 29:34
    next screen, we will discuss about
  • 29:34 - 29:36
    identification and authentication.
  • 29:36 - 29:39
    Identification and authentication
  • 29:39 - 29:42
    involves proving one's identity which is
  • 29:42 - 29:44
    authenticated prior to being granted
  • 29:44 - 29:46
    access. It is a critical building block
  • 29:46 - 29:49
    of IS Security in which the basis of
  • 29:49 - 29:52
    most access control systems: first line
  • 29:52 - 29:54
    of defense, preventing unauthorized
  • 29:54 - 29:58
    access. I&A also establishes user
  • 29:58 - 30:01
    accountability, linking activities to
  • 30:01 - 30:04
    users. Multifactor authentication is a
  • 30:04 - 30:07
    combination of more than one method, for
  • 30:07 - 30:11
    example, token and password or pin, token
  • 30:11 - 30:14
    and biometric device. Let us continue
  • 30:14 - 30:16
    discussing identification and
  • 30:16 - 30:18
    authentication in the next slide.
  • 30:18 - 30:21
    Categories can be something you know, for
  • 30:21 - 30:23
    example, password, something you have, for
  • 30:23 - 30:26
    example, token card, something you are or
  • 30:26 - 30:29
    do, a biometric feature, or where you
  • 30:29 - 30:32
    are. These techniques can be used
  • 30:32 - 30:34
    independently or in combination,
  • 30:34 - 30:36
    single-factor or two-factor
  • 30:36 - 30:39
    authentication. Some of the common
  • 30:39 - 30:41
    vulnerabilities expected are weak
  • 30:41 - 30:44
    authentication methods, potential for
  • 30:44 - 30:47
    bypassing authentication mechanism, lack
  • 30:47 - 30:50
    of confidentiality and integrity of
  • 30:50 - 30:53
    stored authentication information, lack
  • 30:53 - 30:55
    of encryption for transmitted
  • 30:55 - 30:58
    authentication information, lack of user
  • 30:58 - 31:01
    knowledge regarding risks of sharing
  • 31:01 - 31:03
    authentication elements, for example,
  • 31:03 - 31:06
    password. In the next few screens, we will
  • 31:06 - 31:08
    discuss about identification and
  • 31:08 - 31:11
    authentication, logon IDs and passwords.
  • 31:12 - 31:14
    Logon IDs and passwords is a
  • 31:14 - 31:17
    two-phase user identification
  • 31:17 - 31:19
    authentication process based on
  • 31:19 - 31:23
    something you know: logon ID, individual
  • 31:23 - 31:26
    identification, password, individual
  • 31:26 - 31:28
    authentication. It is used to
  • 31:28 - 31:30
    restrict access to computerized
  • 31:30 - 31:33
    information, transactions, programs, and
  • 31:33 - 31:36
    system software. It may involve an
  • 31:36 - 31:39
    internal list of valid logon IDs and a
  • 31:39 - 31:41
    corresponding set of access rules for
  • 31:41 - 31:45
    each logon ID. The access rules can be
  • 31:45 - 31:48
    specified at OS level, controlling access
  • 31:48 - 31:50
    to files, or within individual
  • 31:50 - 31:53
    applications, controlling access to menu
  • 31:53 - 31:56
    functions and types of data. Features of
  • 31:56 - 31:59
    passwords include easy for the user to
  • 31:59 - 32:02
    remember but difficult for a perpetrator
  • 32:02 - 32:05
    to guess, when the user logs on for the
  • 32:05 - 32:07
    first time, the system should force a
  • 32:07 - 32:09
    password change to improve
  • 32:09 - 32:13
    confidentiality, limited number of logon
  • 32:13 - 32:16
    attempts, typically three, user
  • 32:16 - 32:19
    verification for forgotten passwords,
  • 32:19 - 32:21
    internal one-way encryption, and not
  • 32:21 - 32:24
    displayed in any form, changed
  • 32:24 - 32:27
    periodically, for example, every 30 days,
  • 32:27 - 32:30
    unique; if it is known by more than one
  • 32:30 - 32:32
    person, responsibility for activity
  • 32:32 - 32:36
    cannot be enforced. Password syntax
  • 32:36 - 32:39
    format rules: Ideally a minimum of eight
  • 32:39 - 32:42
    characters in length, a combination of at
  • 32:42 - 32:45
    least three of the following alpha,
  • 32:45 - 32:48
    numeric, upper and lower case, and special
  • 32:48 - 32:51
    characters, some prohibit use of vowels,
  • 32:51 - 32:54
    not particularly identifiable to the
  • 32:54 - 32:57
    user, system should enforce regular
  • 32:57 - 32:59
    change of passwords, for example, after
  • 32:59 - 33:03
    every 30 days, no re-use of previous
  • 33:03 - 33:05
    passwords, for example, at least one year
  • 33:05 - 33:08
    after being changed, deactivate dormant
  • 33:08 - 33:12
    logon IDs, automatic session inactivity
  • 33:12 - 33:16
    time-outs, powerful user IDs, accounts, such
  • 33:16 - 33:19
    as Supervisor and Administrator accounts
  • 33:19 - 33:21
    should be strictly controlled; these
  • 33:21 - 33:24
    could have full access to the system,
  • 33:24 - 33:25
    administrator password should be known
  • 33:25 - 33:28
    only by one person, however, the
  • 33:28 - 33:29
    password should be kept in a sealed
  • 33:29 - 33:31
    envelope for business
  • 33:31 - 33:34
    continuity. Let us proceed to the next
  • 33:34 - 33:36
    slide for more on passwords.
  • 33:37 - 33:40
    Token devices and one-time passwords is a
  • 33:40 - 33:42
    two-factor authentication technique, for
  • 33:42 - 33:45
    example, a microprocessor-controlled
  • 33:45 - 33:47
    smart card, which generates unique,
  • 33:47 - 33:50
    time-dependent, one-time passwords called
  • 33:50 - 33:52
    session passwords. This is good for only
  • 33:52 - 33:56
    one logon session. The users enter this
  • 33:56 - 33:57
    password along with the password they
  • 33:57 - 34:00
    have memorized to gain access to the
  • 34:00 - 34:03
    system. It is characterized by unique
  • 34:03 - 34:06
    session characteristic, ID or time,
  • 34:06 - 34:08
    appended to the password. Technique
  • 34:08 - 34:11
    involves something you have, a device
  • 34:11 - 34:13
    subject to theft, and something you know,
  • 34:13 - 34:16
    a pin. In the next screen, we will learn
  • 34:16 - 34:20
    about identification and authentication,
  • 34:20 - 34:22
    biometric access control.
  • 34:23 - 34:26
    Biometric security access control is the best
  • 34:26 - 34:28
    means of authenticating a user's
  • 34:28 - 34:31
    identity based on a unique, measurable
  • 34:31 - 34:33
    attribute or trait for verifying the
  • 34:33 - 34:37
    identity of a human being. It restricts
  • 34:37 - 34:39
    computer access based on a physical,
  • 34:39 - 34:41
    something you are, or behavioral,
  • 34:41 - 34:44
    something you do, feature of the user, for
  • 34:44 - 34:47
    example, a fingerprint or eye retina
  • 34:47 - 34:50
    pattern. A reader interprets the
  • 34:50 - 34:52
    individual's biometric features before
  • 34:52 - 34:55
    permitting authorized access, however, it
  • 34:55 - 34:58
    is not a fool-proof process. Certain
  • 34:58 - 35:01
    biometric features can change, for
  • 35:01 - 35:03
    example, scarred fingerprints, change in
  • 35:03 - 35:06
    voice. The final template is derived
  • 35:06 - 35:08
    through an iterative averaging process
  • 35:08 - 35:11
    of acquiring samples. Let us continue
  • 35:11 - 35:15
    discussing identification and authentication,
  • 35:15 - 35:18
    biometric access control continued.
  • 35:18 - 35:20
    Physically oriented biometrics
  • 35:20 - 35:24
    are palm, hand geometry, iris, retina,
  • 35:24 - 35:27
    fingerprint, face. Behavior oriented
  • 35:27 - 35:30
    biometrics can be signature recognition
  • 35:30 - 35:32
    and voice recognition.
  • 35:32 - 35:34
    In the next few screens, we
  • 35:34 - 35:37
    will discuss about identification and
  • 35:37 - 35:41
    authentication single sign-on, SSO.
  • 35:42 - 35:44
    Single sign-on, SSO, is a
  • 35:44 - 35:47
    consolidation of the organization
  • 35:47 - 35:49
    platform-based administration,
  • 35:49 - 35:51
    authentication, and authorization
  • 35:51 - 35:54
    functions. It interfaces with client
  • 35:54 - 35:57
    server and distributed systems, mainframe
  • 35:57 - 35:59
    systems, and network security including
  • 35:59 - 36:03
    remote access. The primary domain handles
  • 36:03 - 36:04
    the first instance where user
  • 36:04 - 36:06
    credentials are entered and the
  • 36:06 - 36:09
    secondary domain is any other resource
  • 36:09 - 36:10
    that uses these
  • 36:10 - 36:13
    credentials. Single sign on, SSO,
  • 36:13 - 36:17
    challenges: overcoming heterogeneous
  • 36:17 - 36:19
    nature of diverse architecture, networks,
  • 36:19 - 36:23
    platforms, databases, and applications,
  • 36:23 - 36:25
    requires understanding of each system's
  • 36:25 - 36:28
    authorization rules, and audit logs, and
  • 36:28 - 36:31
    reports, allowing host systems to control
  • 36:31 - 36:33
    the set of users allowed access to
  • 36:33 - 36:35
    particular host
  • 36:35 - 36:38
    systems. SSO advantages: multiple
  • 36:38 - 36:41
    passwords not required, users motivated
  • 36:41 - 36:44
    to select stronger passwords, efficiency
  • 36:44 - 36:46
    in managing users and their
  • 36:46 - 36:48
    authorizations, reduced administrative
  • 36:48 - 36:51
    overheads for resetting passwords,
  • 36:51 - 36:53
    efficiency of disabling deactivating
  • 36:53 - 36:58
    user accounts, reduced logon time. SSO
  • 36:58 - 37:01
    disadvantages: single point of network
  • 37:01 - 37:03
    failure, few software solutions
  • 37:03 - 37:07
    accommodate all major OS, substantial
  • 37:07 - 37:09
    interface development required,
  • 37:09 - 37:12
    development costly. In the next screen, we
  • 37:12 - 37:14
    will discuss about logical access
  • 37:14 - 37:16
    security administration.
  • 37:16 - 37:18
    Logical access security
  • 37:18 - 37:21
    administration can be centralized or
  • 37:21 - 37:24
    decentralized. Advantages of
  • 37:24 - 37:26
    decentralized administration:
  • 37:26 - 37:28
    administration on site at
  • 37:28 - 37:31
    distributed location, timely resolution
  • 37:31 - 37:35
    of issues, more frequent monitoring,
  • 37:35 - 37:38
    controlling remote and distributed sites,
  • 37:38 - 37:41
    software access controls, physical access
  • 37:41 - 37:44
    controls, lockable terminals, locked
  • 37:44 - 37:47
    computer rooms, control over dial-in
  • 37:47 - 37:51
    facilities, modems, laptops, controls over
  • 37:51 - 37:52
    access to system
  • 37:52 - 37:55
    documentation, controls over data
  • 37:55 - 37:58
    transmission, access, accuracy,
  • 37:58 - 38:01
    completeness, controls over replicated
  • 38:01 - 38:04
    files and their updates, accuracy and
  • 38:04 - 38:05
    reduced duplication.
  • 38:05 - 38:07
    Let us continue our
  • 38:07 - 38:10
    discussion about logical access security
  • 38:10 - 38:14
    administration. Risks associated with
  • 38:14 - 38:16
    decentralized administration: local
  • 38:16 - 38:18
    standards, rather than organizational, may
  • 38:18 - 38:21
    be implemented, level of security
  • 38:21 - 38:23
    management may be below that of the
  • 38:23 - 38:26
    central site, unavailability of
  • 38:26 - 38:28
    management checks and audits by the
  • 38:28 - 38:31
    central site. In the next screen, we will
  • 38:31 - 38:34
    discuss about remote access security.
  • 38:34 - 38:37
    Business need of remote access
  • 38:37 - 38:39
    provides users with the same
  • 38:39 - 38:40
    functionality that exists within their
  • 38:40 - 38:44
    offices. The components of remote access:
  • 38:44 - 38:47
    remote environment, employees, branches
  • 38:47 - 38:50
    laptops, telecommunication infrastructure,
  • 38:50 - 38:53
    the carrier used, corporate computing
  • 38:53 - 38:55
    infrastructure, corporate connecting
  • 38:55 - 38:58
    devices, communication software.
  • 38:58 - 39:01
    Remote access risks could be denial of
  • 39:01 - 39:04
    service, malicious third-party access,
  • 39:04 - 39:07
    misconfigured communication software,
  • 39:07 - 39:10
    misconfigured devices, host systems not
  • 39:10 - 39:13
    secured appropriately, and physical
  • 39:13 - 39:15
    security weaknesses at the remote
  • 39:15 - 39:17
    stations. Let us continue discussing
  • 39:17 - 39:21
    about remote access security in the next screen.
  • 39:22 - 39:25
    Remote access methods are analog
  • 39:25 - 39:27
    modems and the public telephone network,
  • 39:27 - 39:29
    dedicated network connections,
  • 39:29 - 39:33
    proprietary circuits, and TCP IP
  • 39:33 - 39:36
    internet-based remote access. The remote
  • 39:36 - 39:39
    access controls are policy and standards,
  • 39:39 - 39:43
    proper authorization, identification and
  • 39:43 - 39:46
    authentication mechanisms, encryption
  • 39:46 - 39:49
    tools and techniques, system and network
  • 39:49 - 39:51
    management. In the next screen, we will
  • 39:51 - 39:55
    discuss about PDAs and mobile technology.
  • 39:56 - 39:58
    PDAs augment desktops and
  • 39:58 - 40:00
    laptops due to their ease of use and
  • 40:00 - 40:03
    functionality. The inherent risks is that
  • 40:03 - 40:06
    they are easy to steal, easy to lose,
  • 40:06 - 40:09
    ready access to information stored.
  • 40:09 - 40:11
    Access issues with mobile technologies
  • 40:11 - 40:15
    includes flash disks and controls. Let us
  • 40:15 - 40:18
    continue discussing about PDAs and
  • 40:18 - 40:21
    mobile technology in the next screen.
  • 40:22 - 40:25
    Control issues to address are
  • 40:25 - 40:27
    compliance with policies and procedures,
  • 40:27 - 40:30
    including approval for PDA use,
  • 40:30 - 40:33
    awareness of responsibilities and due
  • 40:33 - 40:36
    care, compliance with security
  • 40:36 - 40:39
    requirements, authorization and approval
  • 40:39 - 40:42
    of use, standard PDA applications,
  • 40:42 - 40:46
    authorized and licensed, synchronization,
  • 40:46 - 40:50
    backup and updating, encryption, virus
  • 40:50 - 40:52
    detection and control, device
  • 40:52 - 40:57
    registration, camera use. Audit logging in
  • 40:57 - 41:01
    monitoring system access. Most access
  • 41:01 - 41:03
    control software automatically log and
  • 41:03 - 41:06
    report all access attempts, success and
  • 41:06 - 41:09
    failures. It provides management with an
  • 41:09 - 41:13
    audit trail to monitor activities. It
  • 41:13 - 41:15
    facilitates accountability.
  • 41:15 - 41:16
    Access rights to system
  • 41:16 - 41:20
    logs should be for review purposes and
  • 41:20 - 41:24
    it is a form of security against modification.
  • 41:24 - 41:26
    Let us continue discussing
  • 41:26 - 41:28
    about system access in the next screen.
  • 41:29 - 41:31
    The tools for analysis of audit
  • 41:31 - 41:35
    log information: audit reduction tools
  • 41:35 - 41:38
    filter out insignificant data, trend
  • 41:38 - 41:41
    variance detection tools, attack
  • 41:41 - 41:44
    signature detection tools, reviewing
  • 41:44 - 41:47
    audit logs, monitors patterns or trends,
  • 41:47 - 41:50
    and violations and/or use of incorrect
  • 41:50 - 41:53
    passwords. Restricting and monitoring
  • 41:53 - 41:55
    access, features that bypass security
  • 41:55 - 41:58
    accessed by software programmers
  • 41:58 - 42:01
    including bypass label processing, BLP,
  • 42:01 - 42:05
    system exits, and special system logon IDs.
  • 42:06 - 42:07
    You will now attempt a question
  • 42:07 - 42:10
    to test what you have learned so far.
  • 42:10 - 42:11
    In this topic, we will learn about the
  • 42:11 - 42:15
    concepts in Knowledge Statement 5.5
  • 42:15 - 42:18
    Let us discuss risks and controls
  • 42:18 - 42:20
    associated with virtualized systems.
  • 42:21 - 42:23
    This slide endeavors to learn
  • 42:23 - 42:25
    risks and controls associated with
  • 42:25 - 42:28
    virtualization of systems.
  • 42:28 - 42:31
    Virtualization provides an organization
  • 42:31 - 42:33
    with a significant opportunity to
  • 42:33 - 42:37
    increase efficiency and decrease costs in
  • 42:37 - 42:39
    its IT operations.
  • 42:39 - 42:41
    The IS auditor needs to know
  • 42:41 - 42:43
    the different advantages and
  • 42:43 - 42:46
    disadvantages and needs to consider
  • 42:46 - 42:48
    whether the enterprise has considered
  • 42:48 - 42:51
    the applicable risks in its decision to
  • 42:51 - 42:53
    adopt, implement, and maintain this
  • 42:53 - 42:56
    technology. At a higher level,
  • 42:56 - 42:58
    virtualization allows multiple
  • 42:58 - 43:02
    operating systems, OSs, or guests, to
  • 43:02 - 43:05
    coexist on the same physical server, or
  • 43:05 - 43:09
    host, in isolation of one another. Let us
  • 43:09 - 43:11
    continue discussing about risks and
  • 43:11 - 43:13
    controls associated with virtualize
  • 43:13 - 43:16
    systems in the next screen.
  • 43:16 - 43:18
    Virtualization creates a layer
  • 43:18 - 43:21
    between the hardware and the guest OSs
  • 43:21 - 43:24
    to manage shared processing and memory
  • 43:24 - 43:28
    resources on the host machine. A management
  • 43:28 - 43:30
    console often provides administrative
  • 43:30 - 43:33
    access to manage the virtualized system.
  • 43:33 - 43:35
    Virtualization introduce additional
  • 43:35 - 43:37
    risks that the enterprise must manage
  • 43:37 - 43:40
    effectively. Key risk is that the host
  • 43:40 - 43:42
    represents a single point of failure
  • 43:42 - 43:45
    within the system. A successful attack on
  • 43:45 - 43:48
    the host could result in a compromise
  • 43:48 - 43:52
    very large in impact. Main areas covered
  • 43:52 - 43:53
    here are
  • 43:53 - 43:56
    virtualization. You will now attempt to
  • 43:56 - 43:58
    question to test what you have learned so far.
  • 43:58 - 44:00
    In this topic, we will learn about
  • 44:00 - 44:03
    the concepts in Knowledge Statement 5.6.
  • 44:03 - 44:06
    Let us discuss network security
  • 44:06 - 44:09
    controls in the next screen. Knowledge of
  • 44:09 - 44:12
    the configuration, implementation,
  • 44:12 - 44:14
    operation, and maintenance of network
  • 44:14 - 44:17
    security controls are what we'll learn
  • 44:17 - 44:20
    in this slide. Enterprises can
  • 44:20 - 44:23
    effectively prevent and detect most
  • 44:23 - 44:25
    attacks on their networks by employing
  • 44:25 - 44:28
    perimeter security controls.
  • 44:28 - 44:31
    Firewalls and intrusion detection system,
  • 44:31 - 44:34
    IDS, provide protection and critical
  • 44:34 - 44:36
    alert information at borders between
  • 44:36 - 44:40
    trusted and untrusted networks. Proper
  • 44:40 - 44:42
    implementation and maintenance of
  • 44:42 - 44:45
    firewalls and IDS is critical to
  • 44:45 - 44:49
    successful, in-depth security program. The
  • 44:49 - 44:51
    IS auditor must understand the level of
  • 44:51 - 44:53
    intruder detection provided by the
  • 44:53 - 44:57
    different possible locations of the IDS
  • 44:57 - 44:58
    and the importance of policies and
  • 44:58 - 45:00
    procedures to determine the action
  • 45:00 - 45:03
    required by security and technical staff
  • 45:03 - 45:06
    when an intruder is reported.
  • 45:06 - 45:09
    Main areas of covered here are
  • 45:09 - 45:12
    internet threats and security. In the
  • 45:12 - 45:14
    next few screens, we will discuss about
  • 45:14 - 45:16
    network infrastructure security.
  • 45:17 - 45:19
    The table demonstrates network
  • 45:19 - 45:21
    infrastructure security.
  • 45:22 - 45:23
    Auditing use of the Internet
  • 45:23 - 45:26
    involves ensuring a business case for
  • 45:26 - 45:29
    email, communication, marketing, customer
  • 45:29 - 45:31
    communication, sales channel or
  • 45:31 - 45:33
    e-commerce, channel for delivery of goods
  • 45:33 - 45:36
    and services, online stores, internet
  • 45:36 - 45:39
    banking, and information gathering,
  • 45:39 - 45:42
    research. Auditing networks. Review
  • 45:42 - 45:45
    network diagrams to identify networking
  • 45:45 - 45:49
    infrastructure and network design. Also
  • 45:49 - 45:51
    review network management, policies,
  • 45:51 - 45:53
    procedures, standards, guidance
  • 45:53 - 45:56
    distributed to staff. Besides identify
  • 45:56 - 45:58
    responsibility for security and
  • 45:58 - 46:01
    operation, and review staff training
  • 46:01 - 46:01
    duties and
  • 46:01 - 46:04
    responsibilities. You will further review
  • 46:04 - 46:06
    legal issues regarding the use of the
  • 46:06 - 46:09
    internet, service level agreements with
  • 46:09 - 46:11
    third parties, and network administrator
  • 46:11 - 46:14
    procedures. Auditing remote access
  • 46:14 - 46:17
    involves identify all remote access
  • 46:17 - 46:19
    facilities, ensuring they have been
  • 46:19 - 46:22
    documented, review policies governing the
  • 46:22 - 46:25
    use of remote access, review architecture,
  • 46:25 - 46:27
    identifying points of entry and
  • 46:27 - 46:30
    assessing their controls, test dial-up
  • 46:30 - 46:33
    access controls, review relation to
  • 46:33 - 46:35
    business requirements. General network
  • 46:35 - 46:38
    controls are functions performed by
  • 46:38 - 46:40
    technically qualified operators. These
  • 46:40 - 46:43
    functions are separated and rotated
  • 46:43 - 46:46
    regularly. Apply least-privilege access
  • 46:46 - 46:48
    rights for operators. Audit trail of
  • 46:48 - 46:51
    operator activities must be periodically
  • 46:51 - 46:54
    reviewed by management. Network operation
  • 46:54 - 46:57
    standards must be documented. A review of
  • 46:57 - 46:59
    workload balance, response times, and
  • 46:59 - 47:03
    system efficiency must also be performed.
  • 47:03 - 47:05
    Further, consider terminal authentication
  • 47:05 - 47:08
    and data encryption. Some of the network
  • 47:08 - 47:10
    management control software include
  • 47:10 - 47:12
    Novel Netware, Windows
  • 47:12 - 47:16
    NT/2000, UNIX. You will now attempt a
  • 47:16 - 47:18
    question to test what you have learned so far.
  • 47:18 - 47:20
    In this topic we will learn about
  • 47:20 - 47:23
    the concepts in Knowledge Statement 5.7.
  • 47:23 - 47:25
    Let us discuss network and internet
  • 47:25 - 47:28
    security devices, protocols, and
  • 47:28 - 47:30
    techniques in the next screen. The key
  • 47:30 - 47:32
    knowledge to learn in this topic is
  • 47:32 - 47:35
    network and internet security devices,
  • 47:35 - 47:39
    protocols, and techniques. Application and
  • 47:39 - 47:41
    evaluation of technologies to reduce
  • 47:41 - 47:45
    risk and secure data is dependent on
  • 47:45 - 47:47
    proper understanding of security devices,
  • 47:47 - 47:50
    their functions, and protocols used in
  • 47:50 - 47:53
    delivering functionality. An organization
  • 47:53 - 47:55
    implements specific applications of
  • 47:55 - 47:57
    cryptographic systems in order to
  • 47:57 - 48:01
    ensure confidentiality of important data.
  • 48:01 - 48:03
    There are a number of cryptographic
  • 48:03 - 48:05
    protocols which provide secure
  • 48:05 - 48:07
    communications on the internet.
  • 48:07 - 48:10
    Additionally, the security landscape is
  • 48:10 - 48:12
    filled with technologies and solutions
  • 48:12 - 48:15
    to address many needs. Solutions include
  • 48:15 - 48:18
    firewalls, intrusion detection and
  • 48:18 - 48:21
    prevention devices, proxy devices, web
  • 48:21 - 48:25
    filters, antivirus and anti-spam filters,
  • 48:25 - 48:27
    data leak protection functionality,
  • 48:27 - 48:30
    identity and access control mechanisms,
  • 48:30 - 48:32
    secured remote access, and wireless
  • 48:32 - 48:35
    security. Understanding the solution's
  • 48:35 - 48:37
    function and its application to the
  • 48:37 - 48:39
    underlying infrastructure requires
  • 48:39 - 48:42
    knowledge of the infrastructure itself
  • 48:42 - 48:45
    and the protocols in use. In the next
  • 48:45 - 48:47
    screen, we will see the main areas to be
  • 48:47 - 48:49
    covered under this topic.
  • 48:50 - 48:52
    Main areas covered here are
  • 48:52 - 48:55
    encryption, network infrastructure
  • 48:55 - 48:58
    security. In the next few screens, we will
  • 48:58 - 49:01
    learn about firewalls. Firewall is a
  • 49:01 - 49:03
    security perimeter for corporate
  • 49:03 - 49:05
    networks connecting to the internet
  • 49:05 - 49:08
    aimed at preventing external intruders
  • 49:08 - 49:11
    and untrusted internal users, internal
  • 49:11 - 49:14
    hackers. It applies rules to control
  • 49:14 - 49:16
    network traffic flowing in and out of a
  • 49:16 - 49:19
    network, allowing users to access the
  • 49:19 - 49:21
    internet and stopping hackers or others
  • 49:21 - 49:24
    on the internet from gaining access to
  • 49:24 - 49:26
    the network. The guiding principle used
  • 49:26 - 49:30
    is least privilege, need-to-use basis.
  • 49:30 - 49:32
    General firewall features include
  • 49:32 - 49:35
    combination of hardware, routers, servers,
  • 49:35 - 49:38
    and software, it should control the most
  • 49:38 - 49:40
    vulnerable point between a corporate
  • 49:40 - 49:43
    network and the internet. General
  • 49:43 - 49:46
    functions of firewalls includes blocking
  • 49:46 - 49:49
    access to particular sites, limiting
  • 49:49 - 49:51
    traffic on public services to relevant
  • 49:51 - 49:54
    ports, preventing access to certain
  • 49:54 - 49:57
    servers and/or services, monitoring and
  • 49:57 - 49:59
    recording communication between internal
  • 49:59 - 50:01
    and external networks, network
  • 50:01 - 50:04
    penetration, internal subversion,
  • 50:04 - 50:07
    encryption and VPN, and single choke
  • 50:07 - 50:10
    point, concentrating security on a single
  • 50:10 - 50:14
    system. General firewall features include
  • 50:14 - 50:17
    combination of hardware, routers, servers,
  • 50:17 - 50:19
    and software, it should control the most
  • 50:19 - 50:21
    vulnerable point between a corporate
  • 50:21 - 50:24
    network and the internet. General
  • 50:24 - 50:27
    techniques used to control traffic are
  • 50:27 - 50:31
    service control, IP address TCP Port,
  • 50:31 - 50:34
    direction control, direction of traffic,
  • 50:34 - 50:37
    user control, based on user rights,
  • 50:37 - 50:39
    behavior control, based on how services
  • 50:39 - 50:42
    are being used, for example, filter email
  • 50:42 - 50:46
    for spam. In the next few screens, we will
  • 50:46 - 50:49
    discuss about types of firewalls.
  • 50:49 - 50:52
    The types of firewalls are
  • 50:52 - 50:54
    router packet filtering, application
  • 50:54 - 50:59
    firewall systems, and stateful inspection firewalls.
  • 50:59 - 51:01
    Router packet filtering
  • 51:01 - 51:03
    firewall is deployed between the private
  • 51:03 - 51:06
    network and the internet. Screening
  • 51:06 - 51:08
    routers examine packet headers to
  • 51:08 - 51:11
    ascertain IP address, identity, of the
  • 51:11 - 51:13
    sender and receiver, and the authorized
  • 51:13 - 51:15
    port numbers allowed to use the
  • 51:15 - 51:18
    information transmitted, kind of Internet
  • 51:18 - 51:21
    service being used. These information is
  • 51:21 - 51:23
    used to prevent certain packets from
  • 51:23 - 51:25
    being sent between the network and the
  • 51:25 - 51:29
    internet. The common attacks against
  • 51:29 - 51:31
    packet filtering are IP spoofing, source
  • 51:31 - 51:34
    routing specification, and miniature
  • 51:34 - 51:37
    fragment attack. This method is simple
  • 51:37 - 51:39
    and stable. The demerit is that it is
  • 51:39 - 51:42
    easily weakened by improperly configured
  • 51:42 - 51:45
    filters. Also, it is unable to prevent
  • 51:45 - 51:48
    attacks tunneled over permitted surface.
  • 51:48 - 51:50
    The diagram in the slide describes this
  • 51:50 - 51:53
    type of firewall. Application firewall
  • 51:53 - 51:57
    systems. This type of firewall allows
  • 51:57 - 51:59
    information flow between internal and
  • 51:59 - 52:02
    external systems, but do not allow direct
  • 52:02 - 52:05
    exchange of packets. Host applications
  • 52:05 - 52:07
    must be secured against threats posed by
  • 52:07 - 52:10
    allowed packets. They rest on hardened
  • 52:10 - 52:14
    operating systems, for example, WinNT,
  • 52:14 - 52:17
    UNIX. It works on the application layer
  • 52:17 - 52:20
    of the OSI model. The firewall analyze
  • 52:20 - 52:22
    packets through a series of proxies, one
  • 52:22 - 52:25
    for each surface. There are two types,
  • 52:25 - 52:28
    application-level firewalls and circuit-level
  • 52:28 - 52:32
    firewalls. Application-level firewalls
  • 52:32 - 52:34
    analyze packets through a series of
  • 52:34 - 52:37
    proxies, one for each service.
  • 52:37 - 52:40
    Circuit-level firewalls validates TCP and UDP
  • 52:40 - 52:42
    sessions through a single general-purpose
  • 52:42 - 52:45
    proxy. The diagram in the slide
  • 52:45 - 52:48
    demonstrates this. Application firewall
  • 52:48 - 52:51
    systems are set up as proxy servers
  • 52:51 - 52:54
    acting on behalf of network users. It
  • 52:54 - 52:57
    employs bastion hosting, and it is
  • 52:57 - 52:59
    heavily fortified against attack,
  • 52:59 - 53:01
    handling all incoming requests from the
  • 53:01 - 53:03
    internet to the network. Single host
  • 53:03 - 53:05
    makes security maintenance easier as
  • 53:05 - 53:08
    only the firewall system is compromised,
  • 53:08 - 53:10
    not the network. In the next screen, we
  • 53:10 - 53:13
    will discuss about types of firewalls
  • 53:13 - 53:17
    and firewall issues. Stateful inspection
  • 53:17 - 53:20
    firewalls track destination IP address
  • 53:20 - 53:22
    of each packet leaving the network and
  • 53:22 - 53:24
    references responses to requests that
  • 53:24 - 53:27
    went out. It maps source IP addresses of
  • 53:27 - 53:30
    incoming packets to destination IP
  • 53:30 - 53:32
    addresses of outgoing requests. It
  • 53:32 - 53:34
    prevents attacks initiated and
  • 53:34 - 53:37
    originated by outsiders. Main advantage
  • 53:37 - 53:39
    is that it is more efficient than
  • 53:39 - 53:42
    application firewall systems. The
  • 53:42 - 53:45
    disadvantage is that it is more complex
  • 53:45 - 53:46
    to administer.
  • 53:46 - 53:49
    Issues related to firewalls:
  • 53:49 - 53:52
    false sense of security, no additional
  • 53:52 - 53:55
    internal controls are needed, weak
  • 53:55 - 53:57
    against internal threats,
  • 53:57 - 53:59
    for example, a disgruntled employee
  • 53:59 - 54:02
    cooperating with an external attacker,
  • 54:02 - 54:04
    cannot protect against attacks that
  • 54:04 - 54:08
    bypass the firewall, for example, modem
  • 54:08 - 54:11
    dial-in, misconfigured firewalls,
  • 54:11 - 54:13
    misunderstanding of what constitutes a
  • 54:13 - 54:17
    firewall, monitoring activities not done
  • 54:17 - 54:20
    regularly. In the next screen, we will
  • 54:20 - 54:22
    discuss about implementation of
  • 54:22 - 54:25
    firewalls. Firewalls can be implemented
  • 54:25 - 54:29
    in three ways: screened-host firewall,
  • 54:29 - 54:32
    dual-homed firewall, and demilitarized
  • 54:32 - 54:36
    zone, screened subnet firewall. In the
  • 54:36 - 54:38
    next screen, we will discuss about
  • 54:38 - 54:40
    screened-host firewall.
  • 54:40 - 54:43
    Screened-host firewall, this
  • 54:43 - 54:45
    method utilizes packet filtering and a
  • 54:45 - 54:50
    bastion host, proxy services. Bastion host
  • 54:50 - 54:52
    connects to the internal network. Packet
  • 54:52 - 54:54
    filtering router installed between the
  • 54:54 - 54:57
    Internet and the bastion host. Intruder
  • 54:57 - 55:00
    has to penetrate two systems before the
  • 55:00 - 55:03
    network is compromised. Internal hosts
  • 55:03 - 55:05
    reside on the same network as the
  • 55:05 - 55:08
    bastion host. Security policies determine
  • 55:08 - 55:10
    whether hosts connect directly to the
  • 55:10 - 55:13
    internet or hosts use proxy services of
  • 55:13 - 55:16
    the bastion host. Next screen, we will
  • 55:16 - 55:19
    discuss about dual-homed firewall.
  • 55:19 - 55:21
    This type of implementation is
  • 55:21 - 55:23
    more restrictive form of screened-host
  • 55:23 - 55:26
    firewall. One interface is established
  • 55:26 - 55:28
    for information servers, and a separate
  • 55:28 - 55:31
    interface for private network hosts.
  • 55:31 - 55:33
    Direct traffic to internal hosts is
  • 55:33 - 55:35
    physically prevented as explained in the
  • 55:35 - 55:38
    diagram In the next screen, we will
  • 55:38 - 55:40
    discuss about demilitarized zone,
  • 55:40 - 55:42
    screened subnet firewall,
  • 55:42 - 55:46
    DMZ. This mode utilizes two packet-filtering
  • 55:46 - 55:49
    routers and a bastion host. It
  • 55:49 - 55:51
    is the most secure firewall system and
  • 55:51 - 55:54
    supports network and application-level
  • 55:54 - 55:56
    security. The separate DMZ functions are
  • 55:56 - 55:59
    an isolated network for public servers,
  • 55:59 - 56:02
    proxy servers, and modem pools. Key
  • 56:02 - 56:04
    benefits are that the intruder must
  • 56:04 - 56:07
    penetrate three separate devices. The
  • 56:07 - 56:09
    private network addresses are not
  • 56:09 - 56:12
    disclosed to the internet. Also, internal
  • 56:12 - 56:14
    systems do not have direct access to the
  • 56:14 - 56:17
    internet. In the next screen, we will
  • 56:17 - 56:19
    discuss about intrusion detection
  • 56:19 - 56:21
    systems, IDS.
  • 56:22 - 56:24
    Intrusion detection systems, IDS,
  • 56:24 - 56:27
    monitor network usage anomalies.
  • 56:27 - 56:29
    It is used together with firewalls and
  • 56:29 - 56:32
    routers. It continuously operates in the
  • 56:32 - 56:34
    background and the administrator is
  • 56:34 - 56:36
    alerted when intrusions are detected. It
  • 56:36 - 56:39
    protects against external and internal
  • 56:39 - 56:44
    misuse. IDS components: sensor, this
  • 56:44 - 56:46
    collects data, network packets, log files,
  • 56:46 - 56:50
    system call traces, analyzer, this
  • 56:50 - 56:52
    receives input from sensors and
  • 56:52 - 56:55
    determines intrusive activity, admin
  • 56:55 - 56:57
    console, user
  • 56:57 - 56:59
    interface. Let us continue discussing
  • 56:59 - 57:02
    about intrusion detection systems, IDS, in
  • 57:02 - 57:06
    the next screen. IDSs are categorized into
  • 57:06 - 57:10
    network-based IDSs, NIDS, which identifies
  • 57:10 - 57:13
    attacks within a network, and host-based
  • 57:13 - 57:16
    IDSs, HIDS, which is configured for a
  • 57:16 - 57:19
    specific environment and monitor
  • 57:19 - 57:23
    internal resources of systems. IDS types
  • 57:23 - 57:26
    are signature based, intrusion patterns
  • 57:26 - 57:28
    stored as signatures and limited by
  • 57:28 - 57:31
    detection rules, statistical based,
  • 57:31 - 57:34
    monitors expected behavior, neural
  • 57:34 - 57:37
    networks, similar to statistical, but
  • 57:37 - 57:40
    adding learning functionality, a
  • 57:40 - 57:43
    signature, statistical combination offers
  • 57:43 - 57:46
    better protection. In the next screen, we
  • 57:46 - 57:48
    will learn about IDS and intrusion
  • 57:48 - 57:50
    prevention systems,
  • 57:50 - 57:53
    IPS. The key features of intrusion
  • 57:53 - 57:56
    detection systems; intrusion detection
  • 57:56 - 58:00
    and alerts, gathering evidence, automated
  • 58:00 - 58:03
    response, for example, disconnect, security
  • 58:03 - 58:06
    policy administration and monitoring,
  • 58:06 - 58:09
    interfaces with system tools, logging
  • 58:09 - 58:13
    facilities. IDS limitations include
  • 58:13 - 58:15
    weaknesses in policy definition,
  • 58:15 - 58:17
    application-level
  • 58:17 - 58:19
    vulnerabilities, backdoors to
  • 58:19 - 58:22
    applications, weaknesses in
  • 58:22 - 58:24
    identification and authentication
  • 58:24 - 58:27
    schemes. Let us continue discussing about
  • 58:27 - 58:32
    IDS and intrusion prevention systems, IPS,
  • 58:32 - 58:35
    in the next screen. Intrusion prevention
  • 58:35 - 58:39
    systems, IPS. IPS is closely related to
  • 58:39 - 58:43
    IDS. It is designed to detect and prevent
  • 58:43 - 58:45
    attacks by predicting an attack before
  • 58:45 - 58:48
    it happens, hence, limiting damage or
  • 58:48 - 58:51
    disruption to systems that are attacked.
  • 58:51 - 58:53
    It must be properly configured and tuned
  • 58:53 - 58:56
    to be effective. In the next screen, we
  • 58:56 - 58:59
    will learn about honeypots and honeynets.
  • 58:59 - 59:02
    Honeypot is a software application
  • 59:02 - 59:04
    that pretends to be an unfortunate
  • 59:04 - 59:07
    server on the Internet and is not set up
  • 59:07 - 59:10
    to actively protect against break-ins.
  • 59:10 - 59:12
    Rather, they act as decoy systems that
  • 59:12 - 59:14
    lure hackers and, therefore, are
  • 59:14 - 59:17
    attractive to hackers. The more a
  • 59:17 - 59:19
    honeypot is targeted by an intruder, the
  • 59:19 - 59:23
    more valuable it becomes. Honeypot is
  • 59:23 - 59:25
    technically related to IDSs and
  • 59:25 - 59:28
    firewalls, but it has no real production
  • 59:28 - 59:32
    value as an active sentinel of networks.
  • 59:32 - 59:35
    The two basic types of honeypots are
  • 59:35 - 59:38
    high interaction, gives hackers a real
  • 59:38 - 59:41
    environment to attack, low interaction,
  • 59:41 - 59:44
    emulate production environments.
  • 59:44 - 59:47
    Honeynet is multiple honeypots networked
  • 59:47 - 59:49
    together to simulate a larger network
  • 59:49 - 59:52
    installation known as a honeynet.
  • 59:52 - 59:54
    Honeynet let hackers break into the false
  • 59:54 - 59:56
    network while allowing
  • 59:56 - 59:58
    investigators to watch their every move
  • 59:58 - 60:00
    by a combination of surveillance
  • 60:00 - 60:03
    technologies. You will now attempt a
  • 60:03 - 60:05
    question to test what you have learned so far.
  • 60:05 - 60:07
    In this topic, we will learn about
  • 60:07 - 60:10
    the concepts in Knowledge Statement 5.8.
  • 60:10 - 60:13
    Let us discuss about information
  • 60:13 - 60:15
    system attack methods and techniques in
  • 60:15 - 60:18
    the next screen. The candidate needs to
  • 60:18 - 60:20
    grasp the knowledge of information
  • 60:20 - 60:22
    system attack methods and techniques
  • 60:22 - 60:25
    covered under this topic risks arise
  • 60:25 - 60:27
    from vulnerable abilities whether
  • 60:27 - 60:31
    technical or human within an environment
  • 60:31 - 60:33
    several attack techniques exploit those
  • 60:33 - 60:35
    vulnerabilities and may originate either
  • 60:35 - 60:38
    within or outside the
  • 60:38 - 60:40
    organization computer attacks can result
  • 60:40 - 60:43
    in proprietary or confidential data
  • 60:43 - 60:46
    being stolen or modified loss of
  • 60:46 - 60:48
    customer confidence and market share
  • 60:48 - 60:51
    embarrassment to management and legal
  • 60:51 - 60:52
    actions against an
  • 60:52 - 60:55
    organization let us continue discussing
  • 60:55 - 60:57
    about information system attack methods
  • 60:57 - 60:59
    and techniques in the next
  • 60:59 - 61:01
    screen understanding the methods
  • 61:01 - 61:03
    techniques and exploits used to
  • 61:03 - 61:06
    compromise an environment provides the
  • 61:06 - 61:09
    is auditor with a more complete context
  • 61:09 - 61:10
    for understanding the risk and
  • 61:10 - 61:14
    organization faces the is auditor should
  • 61:14 - 61:16
    understand enough of these attack types
  • 61:16 - 61:19
    to recognize their risk to the business
  • 61:19 - 61:21
    and how they should be addressed by
  • 61:21 - 61:24
    appropriate controls the is auditor
  • 61:24 - 61:26
    should understand the concept of social
  • 61:26 - 61:28
    engineering since these attacks can
  • 61:28 - 61:30
    circumvent the strongest technical
  • 61:30 - 61:33
    security the only effective control is
  • 61:33 - 61:37
    regular user education main areas
  • 61:37 - 61:40
    covered here are computer crime issues
  • 61:40 - 61:43
    and exposures wireless security threats
  • 61:43 - 61:46
    and risks mitigation in the next few
  • 61:46 - 61:48
    screens we will discuss about computer
  • 61:48 - 61:50
    crime issues and
  • 61:50 - 61:53
    exposures computer crimes can be
  • 61:53 - 61:55
    committed from various sources including
  • 61:55 - 61:58
    computer is the object of the crime
  • 61:58 - 62:00
    perpetrator uses another computer to
  • 62:00 - 62:03
    launch an attack computer is the subject
  • 62:03 - 62:05
    of the crime perpetrator uses computer
  • 62:05 - 62:07
    to commit crime and the target is
  • 62:07 - 62:11
    another computer computer is the tool of
  • 62:11 - 62:14
    the crime perpetrator uses computer to
  • 62:14 - 62:16
    commit crime but the target is not the
  • 62:16 - 62:19
    computer but instead data stored on the
  • 62:19 - 62:22
    computer computer symbolizes the crime
  • 62:22 - 62:25
    perpetrator lures the user of computers
  • 62:25 - 62:27
    to get confidential information
  • 62:27 - 62:30
    for example social engineering methods
  • 62:30 - 62:32
    common attack methods and techniques
  • 62:32 - 62:35
    include alteration attack botn Nets
  • 62:35 - 62:39
    Brute Force attack denial of service dos
  • 62:39 - 62:43
    attack dial-in penetration attack War
  • 62:43 - 62:46
    dialing eavesdropping email bombing and
  • 62:46 - 62:49
    spamming email spoofing more common
  • 62:49 - 62:52
    attack methods and techniques include
  • 62:52 - 62:55
    flooding interrupt attack malicious
  • 62:55 - 62:59
    codes man in the- Middle attack
  • 62:59 - 63:01
    masquerading message
  • 63:01 - 63:05
    modification network analysis packet
  • 63:05 - 63:09
    replay fishing piggybacking race
  • 63:09 - 63:12
    conditions remote maintenance tools
  • 63:12 - 63:16
    resource enumeration and browsing salami
  • 63:16 - 63:20
    spam traffic analysis unauthorized
  • 63:20 - 63:22
    access through the internet and
  • 63:22 - 63:24
    worldwide web
  • 63:24 - 63:26
    www virus
  • 63:26 - 63:30
    worms and spyware War driving War
  • 63:30 - 63:34
    walking War chalking in the next few
  • 63:34 - 63:36
    screens we will learn about local area
  • 63:36 - 63:40
    network land security local area network
  • 63:40 - 63:43
    is faced with a lot of risks examples of
  • 63:43 - 63:47
    these risks are unauthorized access and
  • 63:47 - 63:50
    changes to data Andor programs inability
  • 63:50 - 63:54
    to maintain Version Control limited user
  • 63:54 - 63:56
    verification and potential public Public
  • 63:56 - 64:00
    Access General access as opposed to need
  • 64:00 - 64:03
    to know access impersonation or
  • 64:03 - 64:06
    masquerading as a legitimate landan user
  • 64:06 - 64:10
    internal user sniffing internal user
  • 64:10 - 64:14
    spoofing Virus Infection unlicensed or
  • 64:14 - 64:17
    excessive numbers of software copies
  • 64:17 - 64:20
    destruction of logging and auditing data
  • 64:20 - 64:23
    lack of land administrator experience
  • 64:23 - 64:26
    expertise varying media protocol
  • 64:26 - 64:29
    Hardware network software that make
  • 64:29 - 64:32
    standard management difficult security
  • 64:32 - 64:35
    set aside for operational efficiency
  • 64:35 - 64:37
    land administrative capabilities include
  • 64:37 - 64:40
    declaring ownership of programs and
  • 64:40 - 64:43
    files limiting access to readon record
  • 64:43 - 64:46
    and file locking to prevent simultaneous
  • 64:46 - 64:49
    update and enforcing user ID password
  • 64:49 - 64:50
    sign on
  • 64:50 - 64:53
    procedures in order to understand lands
  • 64:53 - 64:56
    it is Paramount for a candidate to have
  • 64:56 - 64:59
    good knowledge of land topology and
  • 64:59 - 65:02
    network diagram functions performed by
  • 65:02 - 65:05
    the land administrator owner Lan users
  • 65:05 - 65:09
    and user groups applications used on the
  • 65:09 - 65:12
    Lan procedures and standards of network
  • 65:12 - 65:16
    design support naming conventions data
  • 65:16 - 65:19
    security dialup access controls are
  • 65:19 - 65:22
    having encrypted passwords portable PCS
  • 65:22 - 65:24
    dialback procedures and one-time
  • 65:24 - 65:27
    password generators or tokens client
  • 65:27 - 65:30
    server risks include numerous access
  • 65:30 - 65:34
    routes and points increased risk of
  • 65:34 - 65:36
    access to data and processing weaker
  • 65:36 - 65:39
    access controls password change controls
  • 65:39 - 65:42
    or access rules weaker change control
  • 65:42 - 65:45
    and change management inaccurate
  • 65:45 - 65:48
    unauthorized access and changes to
  • 65:48 - 65:51
    systems or data loss of network
  • 65:51 - 65:54
    availability obsolescence of network
  • 65:54 - 65:56
    components unauthorized connection of
  • 65:56 - 65:59
    the network to other networks through
  • 65:59 - 66:01
    modems weak connection to public switch
  • 66:01 - 66:04
    telephone networks application code and
  • 66:04 - 66:07
    data may not be stored on a secure
  • 66:07 - 66:10
    machine client server controls that will
  • 66:10 - 66:13
    ensure security include disabling floppy
  • 66:13 - 66:16
    drives automatic boot or startup batch
  • 66:16 - 66:20
    files login scripts network monitoring
  • 66:20 - 66:23
    devices data encryption environment-wide
  • 66:23 - 66:26
    authentication procedures and
  • 66:26 - 66:28
    application Level Access Control
  • 66:28 - 66:31
    organization of users into functional
  • 66:31 - 66:34
    groups in the next few screens we will
  • 66:34 - 66:37
    discuss about the internet threats the
  • 66:37 - 66:41
    internet is a global TCP IP based system
  • 66:41 - 66:43
    that enables public and private
  • 66:43 - 66:45
    heterogeneous networks to communicate
  • 66:45 - 66:48
    with one another internet threats are
  • 66:48 - 66:51
    categorized into passive attacks
  • 66:51 - 66:55
    involves probing for Network information
  • 66:55 - 66:57
    active attacks intrusion or penetration
  • 66:57 - 67:00
    into a network gaining full control or
  • 67:00 - 67:02
    enough to cause certain threats
  • 67:02 - 67:05
    unauthorized access to modified data
  • 67:05 - 67:08
    Andor programs obtaining sensitive
  • 67:08 - 67:11
    information for personal gain escalating
  • 67:11 - 67:15
    privileges denial of service impact
  • 67:15 - 67:17
    could affect financial legal or
  • 67:17 - 67:20
    Competitive Edge types of passive
  • 67:20 - 67:23
    attacks are network analysis involves
  • 67:23 - 67:26
    creating a profile of a network security
  • 67:26 - 67:29
    infrastructure footprinting system
  • 67:29 - 67:32
    aliases internal addresses potential
  • 67:32 - 67:36
    gateways firewalls vulnerable operating
  • 67:36 - 67:39
    system Services eavesdropping involves
  • 67:39 - 67:41
    gathering information flowing through
  • 67:41 - 67:44
    the network for personal analysis or
  • 67:44 - 67:47
    third parties traffic analysis entails
  • 67:47 - 67:50
    determining the nature of traffic flow
  • 67:50 - 67:53
    between defined hosts active attacks can
  • 67:53 - 67:57
    be in the following ways Brute Force
  • 67:57 - 67:59
    attack this entails launching many
  • 67:59 - 68:02
    attacks to gain unauthorized access for
  • 68:02 - 68:06
    example password cracking masquerading
  • 68:06 - 68:08
    this is presenting an identity other
  • 68:08 - 68:11
    than the original identity which is
  • 68:11 - 68:15
    unauthorized packet replay passively
  • 68:15 - 68:17
    capturing data packets and actively
  • 68:17 - 68:20
    inserting them into the network replayed
  • 68:20 - 68:22
    packets treated as another genuine
  • 68:22 - 68:24
    stream it is effective when data
  • 68:24 - 68:27
    received is interpreted and acted upon
  • 68:27 - 68:30
    without human intervention message
  • 68:30 - 68:33
    modification making unauthorized changes
  • 68:33 - 68:37
    or deletions to captured messages
  • 68:37 - 68:40
    unauthorized access through the Internet
  • 68:40 - 68:43
    tnet passwords transmitted in clear text
  • 68:43 - 68:47
    releasing CGI scripts as shareware
  • 68:47 - 68:50
    client side execution of scripts Java
  • 68:50 - 68:53
    applets denial of service flooding
  • 68:53 - 68:56
    servers with data requests systems are
  • 68:56 - 68:59
    paralyzed genuine users are frustrated
  • 68:59 - 69:03
    with unavailability of system dial in
  • 69:03 - 69:05
    penetration attacks using phone number
  • 69:05 - 69:08
    ranges and social engineering email
  • 69:08 - 69:11
    bombing repeating identical messages to
  • 69:11 - 69:14
    particular addresses email spamming
  • 69:14 - 69:18
    sending messages to numerous users email
  • 69:18 - 69:20
    spoofing altering the identity of the
  • 69:20 - 69:24
    source of the message Trojan horses
  • 69:24 - 69:27
    hiding malicious fraudulent code in an
  • 69:27 - 69:30
    authorized computer program rounding
  • 69:30 - 69:33
    down drawing off small amounts of money
  • 69:33 - 69:35
    from a computerized transaction or
  • 69:35 - 69:38
    account to the perpetrator's account
  • 69:38 - 69:41
    salami technique slicing off truncating
  • 69:41 - 69:42
    small amounts of money from a
  • 69:42 - 69:45
    computerized transaction or account
  • 69:45 - 69:49
    similar to rounding down viruses
  • 69:49 - 69:51
    malicious program code inserted into
  • 69:51 - 69:54
    other executable code that can
  • 69:54 - 69:56
    self-replicate and spread for from
  • 69:56 - 70:00
    computer to computer worms destructive
  • 70:00 - 70:02
    programs that may destroy data or
  • 70:02 - 70:04
    utilize tremendous computer and
  • 70:04 - 70:07
    communication resources do not replicate
  • 70:07 - 70:08
    like
  • 70:08 - 70:12
    viruses logic bombs similar to computer
  • 70:12 - 70:14
    viruses but do not self-replicate
  • 70:14 - 70:17
    destruction or modification of data is
  • 70:17 - 70:19
    programmed to a specific time in the
  • 70:19 - 70:21
    future difficult to detect before they
  • 70:21 - 70:25
    blow up trap doors are exits out of an
  • 70:25 - 70:28
    an authorized program they allow
  • 70:28 - 70:30
    insertion of specific logic such as
  • 70:30 - 70:33
    program interrupts to permit a view of
  • 70:33 - 70:36
    data during processing used by
  • 70:36 - 70:38
    programmers to bypass OS Integrity
  • 70:38 - 70:41
    during debugging and maintenance they
  • 70:41 - 70:43
    are meant to be eliminated in final
  • 70:43 - 70:45
    editing of the code but sometimes
  • 70:45 - 70:47
    forgotten or intentionally left for
  • 70:47 - 70:48
    future
  • 70:48 - 70:52
    access asynchronous attacks these are
  • 70:52 - 70:54
    os-based attacks in a multi-processing
  • 70:54 - 70:57
    environment job scheduling resource
  • 70:57 - 71:00
    scheduling checkpoint restart
  • 71:00 - 71:03
    capabilities checkpoint copy data system
  • 71:03 - 71:06
    parameters security levels attacks
  • 71:06 - 71:09
    involve access to and modification of
  • 71:09 - 71:11
    this data to allow higher priority
  • 71:11 - 71:14
    security results in unauthorized access
  • 71:14 - 71:17
    to data other programs and the
  • 71:17 - 71:21
    OS data leakage involves siphoning or
  • 71:21 - 71:23
    leaking information out of the computer
  • 71:23 - 71:27
    dumping files to paper stealing tape
  • 71:27 - 71:29
    wiretapping this is evees dropping on
  • 71:29 - 71:31
    information being transmitted over
  • 71:31 - 71:35
    telecommunication lines piggybacking is
  • 71:35 - 71:37
    following an authorized person through a
  • 71:37 - 71:40
    secure door also it means electronically
  • 71:40 - 71:42
    attaching to an authorized
  • 71:42 - 71:44
    telecommunications link to intercept and
  • 71:44 - 71:46
    possibly alter
  • 71:46 - 71:49
    Transmissions computer shutdown
  • 71:49 - 71:51
    initiated through terminals or micro
  • 71:51 - 71:54
    computers connected directly online or
  • 71:54 - 71:57
    remotely dialup line to the computer
  • 71:57 - 72:01
    denial of service disrupt or completely
  • 72:01 - 72:03
    deny service to legitimate users
  • 72:03 - 72:06
    networks systems or other
  • 72:06 - 72:08
    resources you will now attempt a
  • 72:08 - 72:10
    question to test what you have learned
  • 72:10 - 72:12
    so far in this topic we will learn about
  • 72:12 - 72:15
    the concepts in knowledge statement
  • 72:15 - 72:18
    5.9 let us discuss about virus detection
  • 72:18 - 72:21
    tools and control techniques in the next
  • 72:21 - 72:24
    screen the key is understanding
  • 72:24 - 72:26
    detection tools and and control
  • 72:26 - 72:29
    techniques for example malware virus
  • 72:29 - 72:30
    detection
  • 72:30 - 72:33
    spyware computer viruses and other
  • 72:33 - 72:35
    malware continue to emerge at increasing
  • 72:35 - 72:38
    rates and sophistication and present
  • 72:38 - 72:41
    significant threats to individuals and
  • 72:41 - 72:43
    organizations layered tools should be
  • 72:43 - 72:45
    implemented and distributed throughout
  • 72:45 - 72:47
    the environment in order to mitigate the
  • 72:47 - 72:50
    ability of this malware to adversely
  • 72:50 - 72:51
    impact the
  • 72:51 - 72:54
    organization antivirus and anti-spam
  • 72:54 - 72:57
    software is an necessary and critical
  • 72:57 - 72:59
    component of an organization security
  • 72:59 - 73:02
    program providing a mechanism to detect
  • 73:02 - 73:05
    contain and notify whenever malicious
  • 73:05 - 73:08
    code is detected it is essential that
  • 73:08 - 73:10
    the is auditor understand not only the
  • 73:10 - 73:12
    need for the implementation of
  • 73:12 - 73:15
    antimalware software but that it should
  • 73:15 - 73:18
    be constantly be updated to ensure that
  • 73:18 - 73:20
    it will detect and eradicate the latest
  • 73:20 - 73:23
    attacks detected by the solutions
  • 73:23 - 73:26
    providers viruses is what we will focus
  • 73:26 - 73:30
    on next main areas are covered here are
  • 73:30 - 73:33
    viruses in the next few screens we will
  • 73:33 - 73:34
    learn about
  • 73:34 - 73:37
    viruses viruses are malicious programs
  • 73:37 - 73:40
    designed to self-propagate by appending
  • 73:40 - 73:42
    to other programs they are easily
  • 73:42 - 73:44
    transmitted via the Internet email
  • 73:44 - 73:47
    attachments local area networks viruses
  • 73:47 - 73:50
    attack four parts of the computer
  • 73:50 - 73:52
    executable program files the file
  • 73:52 - 73:54
    directory system which tracks the
  • 73:54 - 73:57
    location of all the computer's files
  • 73:57 - 74:00
    another area is Boot and systems areas
  • 74:00 - 74:02
    which are needed to start the computer
  • 74:02 - 74:06
    data files is also a target for viruses
  • 74:06 - 74:09
    virus controls available are virus and
  • 74:09 - 74:12
    worm controls management procedural
  • 74:12 - 74:15
    controls technical controls antivirus
  • 74:15 - 74:18
    software periodically updated Hardware
  • 74:18 - 74:21
    controls remote booting boot virus
  • 74:21 - 74:23
    protection antivirus software
  • 74:23 - 74:26
    implementation strategies
  • 74:26 - 74:30
    Dynamic antivirus program sound policies
  • 74:30 - 74:33
    and procedures let us continue to
  • 74:33 - 74:36
    discuss viruses on the next slide
  • 74:36 - 74:39
    antivirus software implementation
  • 74:39 - 74:42
    strategies detecting the virus at its
  • 74:42 - 74:45
    point of entry is crucial at user
  • 74:45 - 74:46
    workstation level through scheduled
  • 74:46 - 74:50
    continuous and manual OnDemand scans at
  • 74:50 - 74:52
    corporate Network level as part of the
  • 74:52 - 74:56
    firewall virus wall SMTP
  • 74:56 - 74:59
    HTTP and FTP protection besides
  • 74:59 - 75:02
    automatically updating antivirus
  • 75:02 - 75:06
    software features of antivirus software
  • 75:06 - 75:09
    it should be reliable and offer quality
  • 75:09 - 75:11
    of detection it should be Memory
  • 75:11 - 75:13
    resident to facilitate continuous
  • 75:13 - 75:15
    checking it should as well have
  • 75:15 - 75:18
    efficient working speed and use of
  • 75:18 - 75:22
    resources types of antivirus software
  • 75:22 - 75:26
    scanners virus masks or signatures heris
  • 75:26 - 75:28
    scanners based on statistical
  • 75:28 - 75:31
    probability active monitors looking for
  • 75:31 - 75:32
    virus-like
  • 75:32 - 75:36
    activity Integrity CRC Checkers used to
  • 75:36 - 75:39
    detect changes in files and executable
  • 75:39 - 75:42
    code Behavior blockers focus on
  • 75:42 - 75:45
    detecting potentially abnormal behavior
  • 75:45 - 75:48
    for example writing to the boot sector
  • 75:48 - 75:51
    immunizers append themselves to files
  • 75:51 - 75:54
    and continuously check for changes you
  • 75:54 - 75:56
    will now attempt to question to test
  • 75:56 - 75:59
    what you have learned so far in this
  • 75:59 - 76:01
    topic we will learn about the concepts
  • 76:01 - 76:03
    in knowledge statement
  • 76:03 - 76:06
    5.10 let us discuss about security
  • 76:06 - 76:09
    testing techniques in the next
  • 76:09 - 76:11
    screen it is Paramount for cesa
  • 76:11 - 76:13
    candidates to have knowledge of security
  • 76:13 - 76:16
    testing techniques for example intrusion
  • 76:16 - 76:20
    testing vulnerability scanning tools are
  • 76:20 - 76:22
    available to assess the effectiveness of
  • 76:22 - 76:25
    network infrastructure security these to
  • 76:25 - 76:27
    tools permit identification of real-time
  • 76:27 - 76:29
    risks to an information processing
  • 76:29 - 76:32
    environment and corrective actions taken
  • 76:32 - 76:35
    to mitigate these risks such risks often
  • 76:35 - 76:37
    involve the failure to stay updated on
  • 76:37 - 76:40
    patch management for operating systems
  • 76:40 - 76:42
    or the misconfiguration of security
  • 76:42 - 76:45
    settings assessment tools whether open-
  • 76:45 - 76:47
    Source or commercially produced can
  • 76:47 - 76:50
    quickly identify weaknesses that would
  • 76:50 - 76:52
    have taken hundreds of hours to identify
  • 76:52 - 76:55
    manually the is auditor should also be
  • 76:55 - 76:57
    aware that security testing may be
  • 76:57 - 76:59
    carried out by an approved third party
  • 76:59 - 77:02
    for example a company specializing in
  • 77:02 - 77:05
    penetration testing let us see the main
  • 77:05 - 77:07
    area to cover under this topic in the
  • 77:07 - 77:11
    next screen main areas covered here are
  • 77:11 - 77:14
    auditing Network infrastructure Security
  • 77:14 - 77:16
    in the next few screens we will learn
  • 77:16 - 77:19
    about Network infrastructure security
  • 77:19 - 77:21
    network penetration testing is also
  • 77:21 - 77:24
    called intrusion tests or ethical
  • 77:24 - 77:26
    hacking it involves using techniques
  • 77:26 - 77:29
    available to a hacker open-source
  • 77:29 - 77:32
    intelligence gathering and Discovery
  • 77:32 - 77:35
    attempting to guess passwords searching
  • 77:35 - 77:38
    for back doors into systems exploiting
  • 77:38 - 77:41
    known operating system
  • 77:41 - 77:43
    vulnerabilities it is popular for
  • 77:43 - 77:46
    testing firewalls only performed by
  • 77:46 - 77:48
    skilled experienced professionals it
  • 77:48 - 77:51
    requires permission from top level
  • 77:51 - 77:53
    Senior Management but without informing
  • 77:53 - 77:56
    is security staff
  • 77:56 - 77:58
    you will now attempt a question to test
  • 77:58 - 78:00
    what you have learned so far in this
  • 78:00 - 78:01
    topic we will learn about the concepts
  • 78:01 - 78:04
    in knowledge statement
  • 78:04 - 78:07
    5.11 let us discuss about risks and
  • 78:07 - 78:09
    controls Associated data leakage in the
  • 78:09 - 78:10
    next
  • 78:10 - 78:13
    screen data leakage is the risk that
  • 78:13 - 78:15
    sensitive information may be
  • 78:15 - 78:18
    inadvertently made public it occurs in
  • 78:18 - 78:20
    different ways such as job postings that
  • 78:20 - 78:22
    list the specific software and network
  • 78:22 - 78:25
    devices with which applicants should
  • 78:25 - 78:27
    have experience in to system
  • 78:27 - 78:30
    administrators posting questions on
  • 78:30 - 78:32
    technical websites that include posting
  • 78:32 - 78:34
    with the specific details on the
  • 78:34 - 78:37
    firewall or database version they are
  • 78:37 - 78:39
    running and the IP addresses they are
  • 78:39 - 78:42
    trying to connect posting organization
  • 78:42 - 78:45
    charts and strategic plans to externally
  • 78:45 - 78:48
    accessible websites data classification
  • 78:48 - 78:52
    policies security awareness training and
  • 78:52 - 78:54
    periodic audits of data leakage are
  • 78:54 - 78:56
    elements that the is auditor will want
  • 78:56 - 79:00
    to ensure are in place main areas to be
  • 79:00 - 79:03
    covered here are computer crime issues
  • 79:03 - 79:06
    and exposures let us proceed to the next
  • 79:06 - 79:08
    Topic in this domain in this topic we
  • 79:08 - 79:10
    will learn about the concepts in
  • 79:10 - 79:12
    knowledge statement
  • 79:12 - 79:15
    5.12 let us discuss about Network
  • 79:15 - 79:17
    infrastructure security encryption in
  • 79:17 - 79:20
    the next few screens it is important for
  • 79:20 - 79:22
    cesa candidates to have a good knowledge
  • 79:22 - 79:25
    of encryption related techniques one of
  • 79:25 - 79:27
    the best ways to protect the
  • 79:27 - 79:30
    confidentiality of information is
  • 79:30 - 79:33
    through the use of encryption effective
  • 79:33 - 79:36
    encryption systems depend on algorithm
  • 79:36 - 79:39
    strength secrecy and difficulty of
  • 79:39 - 79:42
    compromising a key the non-existence of
  • 79:42 - 79:45
    back doors by which an encrypted file
  • 79:45 - 79:48
    can be decrypted without knowing the key
  • 79:48 - 79:51
    the inability to decrypt an entire
  • 79:51 - 79:54
    Cipher text message if one knows the way
  • 79:54 - 79:57
    a portion of it Crypts is known this is
  • 79:57 - 80:00
    called known text attack properties of
  • 80:00 - 80:03
    the plain text being known by a
  • 80:03 - 80:06
    perpetrator although the is auditor is
  • 80:06 - 80:08
    not expected to be an expert in how
  • 80:08 - 80:10
    these algorithms are designed the
  • 80:10 - 80:13
    auditor should be able to understand how
  • 80:13 - 80:15
    these techniques are used and the
  • 80:15 - 80:18
    relative advantages and disadvantages of
  • 80:18 - 80:21
    each we will cover encryption techniques
  • 80:21 - 80:25
    in this section main areas to be covered
  • 80:25 - 80:27
    here are
  • 80:27 - 80:30
    encryption encryption means converting
  • 80:30 - 80:33
    plain text messages into secure coded
  • 80:33 - 80:36
    text Cipher text it is done via a
  • 80:36 - 80:38
    mathematical function and a key a
  • 80:38 - 80:41
    special encryption decryption password
  • 80:41 - 80:44
    encryption is used to protect data in
  • 80:44 - 80:46
    transit over networks protect
  • 80:46 - 80:49
    information stored on computers deter
  • 80:49 - 80:52
    and detect alterations of data and
  • 80:52 - 80:54
    verify authenticity of a transaction or
  • 80:54 - 80:58
    do document note we assume that the more
  • 80:58 - 81:00
    difficult it is to decrypt the cipher
  • 81:00 - 81:03
    text the better key elements of
  • 81:03 - 81:07
    encryption systems encryption algorithm
  • 81:07 - 81:09
    mathematical function calculation
  • 81:09 - 81:12
    encryption key piece of information used
  • 81:12 - 81:15
    in the algorithm to make the process
  • 81:15 - 81:18
    unique key length predetermined length
  • 81:18 - 81:22
    of key effectiveness of encryption is
  • 81:22 - 81:24
    based on secrecy and difficulty of
  • 81:24 - 81:27
    compromise iing the key lack of other
  • 81:27 - 81:29
    means of decrypting without the key
  • 81:29 - 81:33
    inability to perform a known text attack
  • 81:33 - 81:36
    knowing how a portion of encrypted text
  • 81:36 - 81:39
    decrypts tradeoffs in encryption if the
  • 81:39 - 81:41
    algorithm is too complex and it takes
  • 81:41 - 81:44
    too long to use or requires keys that
  • 81:44 - 81:47
    are too large to store easily it becomes
  • 81:47 - 81:50
    impractical to use the need to balance
  • 81:50 - 81:52
    between the strength of the encryption
  • 81:52 - 81:54
    that is how difficult it is for someone
  • 81:54 - 81:57
    to discover the algorithm and the key
  • 81:57 - 82:00
    and ease of use there are two main types
  • 82:00 - 82:02
    of encryption in use for computer
  • 82:02 - 82:06
    security referred to as symmetric and
  • 82:06 - 82:09
    asymmetric key encryption these are
  • 82:09 - 82:11
    based on symmetric encryption algorithm
  • 82:11 - 82:14
    same key private to encrypt plain text
  • 82:14 - 82:16
    and decrypt Cipher text also called
  • 82:16 - 82:20
    private or secret key cryptography the
  • 82:20 - 82:22
    common private Key cryptographic Systems
  • 82:22 - 82:27
    are data encryption systems Dees 64-bit
  • 82:27 - 82:31
    Advanced encryption standard AES 128bit
  • 82:31 - 82:32
    to
  • 82:32 - 82:35
    256bit the advantage of this method is
  • 82:35 - 82:38
    that it uses one key to encrypt and
  • 82:38 - 82:41
    decrypt and hence uses less processing
  • 82:41 - 82:44
    power however getting the key to those
  • 82:44 - 82:46
    you want to exchange data with is the
  • 82:46 - 82:49
    problem an illustration of symmetric key
  • 82:49 - 82:51
    cryptographic system is on the next
  • 82:51 - 82:55
    slide Key Management is an issue each
  • 82:55 - 82:57
    pair of communicating entities needs a
  • 82:57 - 83:00
    shared key for an N party system there
  • 83:00 - 83:04
    are n n minus one/ two distinct keys in
  • 83:04 - 83:06
    the system and each party needs to
  • 83:06 - 83:09
    maintain n minus one distinct
  • 83:09 - 83:12
    Keys how to reduce the number of shared
  • 83:12 - 83:15
    keys in the system centralized Key
  • 83:15 - 83:19
    Management session Keys use public Keys
  • 83:19 - 83:22
    asymmetric public Key cryptographic
  • 83:22 - 83:25
    Systems this system uses different keys
  • 83:25 - 83:28
    for encrypting and decrypting a message
  • 83:28 - 83:30
    it solves the problem of getting the key
  • 83:30 - 83:33
    to those you want to exchange data with
  • 83:33 - 83:36
    it involves two keys working as a pair
  • 83:36 - 83:39
    one to encrypt and the other to decrypt
  • 83:39 - 83:42
    a symmetric equals inversely related to
  • 83:42 - 83:45
    each other one key secret private is
  • 83:45 - 83:48
    known only to one person the other key
  • 83:48 - 83:51
    public is known to many people common
  • 83:51 - 83:55
    form of asymmetric encryption is RSA
  • 83:55 - 83:57
    Smith has two keys public and private
  • 83:57 - 84:00
    Smith publishes her public key such that
  • 84:00 - 84:03
    the key is publicly known Smith keeps
  • 84:03 - 84:06
    her private key secret other people use
  • 84:06 - 84:08
    Smith's public key to encrypt messages
  • 84:08 - 84:12
    for Smith Smith uses her private key to
  • 84:12 - 84:16
    decrypt messages only Smith can decrypt
  • 84:16 - 84:19
    since only she has the private key
  • 84:19 - 84:21
    advantages of public key cryptography
  • 84:21 - 84:24
    are the necessity of Distributing Secret
  • 84:24 - 84:27
    keys to large numbers of users is
  • 84:27 - 84:30
    eliminated the algorithm can be used for
  • 84:30 - 84:32
    authentication as well as for creating
  • 84:32 - 84:36
    Cipher text to compute the private key
  • 84:36 - 84:39
    from the public key is assumed difficult
  • 84:39 - 84:42
    public key cryptography ensures
  • 84:42 - 84:44
    authentication and non-repudiation
  • 84:44 - 84:48
    encrypting with the sender's secret key
  • 84:48 - 84:50
    confidentiality encrypting with the
  • 84:50 - 84:53
    receiver's public key authentication and
  • 84:53 - 84:55
    confidentiality for first encrypting
  • 84:55 - 84:57
    with the sender's secret key and
  • 84:57 - 85:01
    secondly with the receiver's public key
  • 85:01 - 85:03
    let us learn the differences between
  • 85:03 - 85:06
    symmetric key and public key in the next
  • 85:06 - 85:09
    screen in symmetric key encryption the
  • 85:09 - 85:12
    two parties must trust each other
  • 85:12 - 85:15
    typically both share the same key
  • 85:15 - 85:17
    symmetric key encryption is generally
  • 85:17 - 85:20
    100 times faster than public key
  • 85:20 - 85:25
    encryption examples include Dees Ida or
  • 85:25 - 85:26
    rc5
  • 85:26 - 85:29
    AES in public key encryption the two
  • 85:29 - 85:32
    parties do not need to trust each other
  • 85:32 - 85:35
    there are two separate Keys a public key
  • 85:35 - 85:38
    and a private key it is slower than
  • 85:38 - 85:41
    symmetric key encryption examples are
  • 85:41 - 85:45
    RSA elgamal encryption
  • 85:45 - 85:50
    ECC elliptical curve cryptography ECC a
  • 85:50 - 85:52
    variant and more efficient form of
  • 85:52 - 85:54
    public key cryptography how to manage
  • 85:54 - 85:57
    more security out of minimum resources
  • 85:57 - 85:59
    gaining prominence is the elliptical
  • 85:59 - 86:04
    curve crypto system Quantum cryptography
  • 86:04 - 86:06
    the next generation of cryptography that
  • 86:06 - 86:08
    will solve existing problems associated
  • 86:08 - 86:11
    with current cryptographic systems
  • 86:11 - 86:13
    Advanced encryption standard
  • 86:13 - 86:17
    AES AES replaces data encryption
  • 86:17 - 86:20
    standard Dees as the cryptographic
  • 86:20 - 86:23
    algorithm standard due to its short key
  • 86:23 - 86:25
    length the former standard for symmetric
  • 86:25 - 86:28
    encryption Dees reach the end of its
  • 86:28 - 86:29
    life
  • 86:29 - 86:33
    cycle digital signatures electronic
  • 86:33 - 86:36
    identification of a person or entity
  • 86:36 - 86:38
    intended for the recipient to verify the
  • 86:38 - 86:40
    Integrity of the data and the identity
  • 86:40 - 86:44
    of the sender data signature ensures
  • 86:44 - 86:47
    data Integrity one-way cryptographic
  • 86:47 - 86:50
    hashing algorithm digital signature
  • 86:50 - 86:53
    algorithms server identity
  • 86:53 - 86:56
    authentication public key cryptography
  • 86:56 - 86:59
    non-repudiation replay protection
  • 86:59 - 87:01
    timestamps and sequence numbers are
  • 87:01 - 87:05
    built into the messages digital envelope
  • 87:05 - 87:07
    used to send encrypted information and
  • 87:07 - 87:10
    the relevant key along with it the
  • 87:10 - 87:12
    message to be sent can be encrypted by
  • 87:12 - 87:15
    using either asymmetric key or symmetric
  • 87:15 - 87:18
    key you will now attempt a question to
  • 87:18 - 87:20
    test what you have learned so far in
  • 87:20 - 87:21
    this topic we will learn about the
  • 87:21 - 87:24
    concepts in knowledge statement 5.1
  • 87:24 - 87:28
    three let us discuss about public key
  • 87:28 - 87:31
    infrastructure pki and digital signature
  • 87:31 - 87:34
    techniques in the next few screens
  • 87:34 - 87:37
    encryption is the process of converting
  • 87:37 - 87:40
    a plain text message into a secure coded
  • 87:40 - 87:43
    form of text called Cipher text which
  • 87:43 - 87:45
    cannot be understood without converting
  • 87:45 - 87:48
    back via decryption the reverse process
  • 87:48 - 87:52
    to plane text pkis use encryption to
  • 87:52 - 87:55
    facilitate the following prect prot data
  • 87:55 - 87:57
    in transit over networks from
  • 87:57 - 87:59
    unauthorized interception and
  • 87:59 - 88:01
    manipulation protect information stored
  • 88:01 - 88:04
    on computers from unauthorized viewing
  • 88:04 - 88:07
    and manipulation deter and detect
  • 88:07 - 88:10
    accidental or intentional alterations of
  • 88:10 - 88:13
    data verify authenticity of a
  • 88:13 - 88:16
    transaction or document for example when
  • 88:16 - 88:18
    transmitted over a web-based connection
  • 88:18 - 88:22
    in online banking share dealing Etc
  • 88:22 - 88:24
    protect data in such situations from
  • 88:24 - 88:26
    unauthorized
  • 88:26 - 88:28
    disclosure understanding the business
  • 88:28 - 88:31
    use of digital signatures is also
  • 88:31 - 88:33
    expected especially its use in providing
  • 88:33 - 88:36
    non-repudiation of and replay protection
  • 88:36 - 88:40
    to messages main areas covered here are
  • 88:40 - 88:44
    encryption public key infrastructure pki
  • 88:44 - 88:46
    in the next few screens we will discuss
  • 88:46 - 88:49
    about public key infrastructure
  • 88:49 - 88:53
    pki public key infrastructure pki
  • 88:53 - 88:55
    framework by which a trust Ed party
  • 88:55 - 88:58
    issues maintains and revokes public key
  • 88:58 - 89:02
    certificates pki reasons many
  • 89:02 - 89:05
    applications need key distribution
  • 89:05 - 89:08
    digital signature vulnerability senders
  • 89:08 - 89:10
    private key and public key may be faked
  • 89:10 - 89:13
    or intercepted and changed anyone can
  • 89:13 - 89:16
    derive keys so there is a need to have a
  • 89:16 - 89:18
    mechanism to assure that Keys belong to
  • 89:18 - 89:22
    entities they claim to come from in pki
  • 89:22 - 89:26
    a certification Authority CA validates
  • 89:26 - 89:30
    Keys distribution in pki is done via a
  • 89:30 - 89:31
    hierarchy of
  • 89:31 - 89:36
    Casa CA process the ca checks real world
  • 89:36 - 89:39
    credentials gets key from user iners
  • 89:39 - 89:42
    signs certificate seert validating key
  • 89:42 - 89:45
    then a certificate is attached to assure
  • 89:45 - 89:47
    an endpoint that an entity is who it
  • 89:47 - 89:50
    claims to be if the endpoint trusts the
  • 89:50 - 89:52
    ca then it will trust that entity and
  • 89:52 - 89:56
    who it claimed to be elements of pki
  • 89:56 - 90:00
    include digital certificates certificate
  • 90:00 - 90:05
    Authority CA registration Authority ra
  • 90:05 - 90:08
    certificate revocation list
  • 90:08 - 90:12
    crl certification practice statement
  • 90:12 - 90:15
    CPS digital
  • 90:15 - 90:17
    certificates digital credential
  • 90:17 - 90:19
    compromising a public key of an
  • 90:19 - 90:22
    individual and identifying information
  • 90:22 - 90:25
    about the individual it is is digitally
  • 90:25 - 90:27
    signed by The Trusted entity with its
  • 90:27 - 90:30
    private key receiver relies on the
  • 90:30 - 90:33
    public key of The Trusted party it also
  • 90:33 - 90:36
    includes algorithm used and validity
  • 90:36 - 90:41
    period certificate Authority CA trusted
  • 90:41 - 90:44
    provider of public and private key pairs
  • 90:44 - 90:47
    attest to the authenticity of owner of
  • 90:47 - 90:51
    public key uses due diligence to issue
  • 90:51 - 90:54
    certificate on evidence or knowledge
  • 90:54 - 90:57
    upon on verification of the user the ca
  • 90:57 - 91:00
    signs the certificate using its private
  • 91:00 - 91:02
    key responsible for managing the
  • 91:02 - 91:05
    certificate throughout its life cycle
  • 91:05 - 91:08
    authoritative for the name or key space
  • 91:08 - 91:09
    it
  • 91:09 - 91:12
    represents certificate revocation list
  • 91:12 - 91:15
    crl details digital certificates that
  • 91:15 - 91:18
    are no longer valid it is used for
  • 91:18 - 91:20
    checking continued validity of
  • 91:20 - 91:23
    certificates time gaps between two
  • 91:23 - 91:25
    updates are very critical
  • 91:25 - 91:28
    certification practice statement CPS is
  • 91:28 - 91:31
    a detailed set of rules governing ca's
  • 91:31 - 91:34
    operations it provides understanding of
  • 91:34 - 91:36
    the value and trustworthiness of
  • 91:36 - 91:39
    certificates issued in terms of controls
  • 91:39 - 91:41
    observed method used to authenticate
  • 91:41 - 91:45
    applicants ca's expectations on how
  • 91:45 - 91:48
    certificates may be used registration
  • 91:48 - 91:52
    Authority R A optional entity separate
  • 91:52 - 91:54
    from the ca that performs admin
  • 91:54 - 91:56
    ministrative tasks like recording and
  • 91:56 - 91:59
    verifying information needed by the ca
  • 91:59 - 92:01
    to issue certifications or
  • 92:01 - 92:04
    crls also performing certificate
  • 92:04 - 92:07
    management functions CA remains solely
  • 92:07 - 92:08
    responsible for signing digital
  • 92:08 - 92:10
    certificates or
  • 92:10 - 92:13
    crls you will now attempt to question to
  • 92:13 - 92:15
    test what you have learned so far in
  • 92:15 - 92:17
    this topic we will learn about the
  • 92:17 - 92:20
    concepts in knowledge statement
  • 92:20 - 92:22
    5.14 let us discuss about peer-to-peer
  • 92:22 - 92:26
    Computing inst messaging and web-based
  • 92:26 - 92:29
    Technologies in the next screen cesa
  • 92:29 - 92:31
    candidates must have a knowledge of
  • 92:31 - 92:33
    risks and controls associated with
  • 92:33 - 92:36
    peer-to-peer Computing instant messaging
  • 92:36 - 92:38
    and web-based Technologies for example
  • 92:38 - 92:42
    social networking message boards blogs
  • 92:42 - 92:44
    peer-to-peer Computing instant messaging
  • 92:44 - 92:47
    and web-based Technologies for example
  • 92:47 - 92:50
    social networks message boards blogs are
  • 92:50 - 92:52
    technologies that introduce new risk to
  • 92:52 - 92:55
    the Enterprise information posted on
  • 92:55 - 92:57
    social network sites May inadvertently
  • 92:57 - 93:00
    disclose confidential non-public
  • 93:00 - 93:02
    information that may violate Financial
  • 93:02 - 93:05
    Security laws or violate customer
  • 93:05 - 93:08
    privacy laws peer-to-peer Computing is
  • 93:08 - 93:11
    inherently insecure and may lead to the
  • 93:11 - 93:13
    introduction of malicious code into an
  • 93:13 - 93:17
    otherwise secure environment main areas
  • 93:17 - 93:19
    to be covered here are computer crime
  • 93:19 - 93:22
    issues and exposures peer-to-peer
  • 93:22 - 93:24
    Computing instant messaging and
  • 93:24 - 93:27
    web-based Technologies in the next
  • 93:27 - 93:28
    screen we'll learn more about
  • 93:28 - 93:30
    peer-to-peer
  • 93:30 - 93:33
    Computing in peer-to-peer Computing no
  • 93:33 - 93:35
    specific server to which a user connects
  • 93:35 - 93:37
    generally connection is between two
  • 93:37 - 93:40
    peers as a result there are risks
  • 93:40 - 93:42
    associated with peer-to-peer which
  • 93:42 - 93:45
    include no Central server hence the
  • 93:45 - 93:47
    risks include virus infected files can
  • 93:47 - 93:50
    be directly shared with others Trojans
  • 93:50 - 93:53
    and spyware may be inadvertently copied
  • 93:53 - 93:55
    across systems
  • 93:55 - 93:58
    users May expose their IP addresses that
  • 93:58 - 94:01
    could result in for example IP spoofing
  • 94:01 - 94:03
    traffic sniffing and other IP based
  • 94:03 - 94:06
    attacks a user from the pier network May
  • 94:06 - 94:08
    access sensitive data in unprotected
  • 94:08 - 94:11
    folders proper security policies and
  • 94:11 - 94:13
    control measures are required for
  • 94:13 - 94:16
    peer-to-peer Computing safest approach
  • 94:16 - 94:19
    is to deny such connections unless there
  • 94:19 - 94:22
    is a business need in the next screen we
  • 94:22 - 94:25
    will learn about instant messaging
  • 94:25 - 94:28
    instant messaging I am is a popular
  • 94:28 - 94:31
    mechanism for collaboration and keeping
  • 94:31 - 94:33
    in touch involves two or more users
  • 94:33 - 94:35
    connecting and chatting on topics of
  • 94:35 - 94:38
    Interest with prompt acknowledgement and
  • 94:38 - 94:41
    response rather than emails risks of
  • 94:41 - 94:44
    instant messaging are eavesdropping if
  • 94:44 - 94:46
    sensitive information is sent over
  • 94:46 - 94:49
    unencrypted channels exchange of virus
  • 94:49 - 94:52
    infected files and other malicious codes
  • 94:52 - 94:54
    data leakage if the file is and
  • 94:54 - 94:57
    unmonitored over IM channels
  • 94:57 - 94:59
    exploitation of vulnerabilities if the
  • 94:59 - 95:02
    public IM client software is not
  • 95:02 - 95:03
    adequately
  • 95:03 - 95:07
    patched controls good IM policy and user
  • 95:07 - 95:10
    awareness required advisable to use
  • 95:10 - 95:13
    internal IM software instead of public
  • 95:13 - 95:15
    software only Enterprise employees
  • 95:15 - 95:18
    should be allowed to connect and
  • 95:18 - 95:20
    adequate monitoring of IM use to
  • 95:20 - 95:22
    minimize risk of data leakage of
  • 95:22 - 95:24
    confidential information
  • 95:24 - 95:27
    in the next slide we will discuss about
  • 95:27 - 95:30
    social networking sites social
  • 95:30 - 95:33
    networking sites SNS include sites such
  • 95:33 - 95:36
    as Facebook and Linkedin that help
  • 95:36 - 95:38
    establish connection with colleagues
  • 95:38 - 95:42
    friends and relatives risks uploading of
  • 95:42 - 95:45
    personal and private information fishing
  • 95:45 - 95:47
    URL spoofing
  • 95:47 - 95:50
    cyberstalking controls policies on what
  • 95:50 - 95:53
    information can be shared on such sites
  • 95:53 - 95:56
    educ ation and awareness to staff on
  • 95:56 - 95:58
    what information to share or not share
  • 95:58 - 96:01
    on such sites also having a policy
  • 96:01 - 96:05
    Banning use of such sites in the office
  • 96:05 - 96:07
    let us continue discussing social
  • 96:07 - 96:09
    networking sites in the next
  • 96:09 - 96:12
    screen example of an incident a hacker
  • 96:12 - 96:14
    was able to gather information about
  • 96:14 - 96:17
    names of friends and date of birth of an
  • 96:17 - 96:19
    employee they use this information to do
  • 96:19 - 96:22
    email spoofing and manag to receive
  • 96:22 - 96:24
    money from the Friends by impersonating
  • 96:24 - 96:26
    him and claiming to be stranded in
  • 96:26 - 96:29
    another country with no passport and
  • 96:29 - 96:31
    money you will now attempt to question
  • 96:31 - 96:34
    to test what you have learned so far in
  • 96:34 - 96:35
    this topic we will learn about the
  • 96:35 - 96:38
    concepts in knowledge statement
  • 96:38 - 96:41
    5.15 let us discuss about controls and
  • 96:41 - 96:44
    risks associated with the use of mobile
  • 96:44 - 96:47
    and wireless devices in the next screen
  • 96:47 - 96:49
    the cesa candidate must have a knowledge
  • 96:49 - 96:51
    of controls and risks associated with
  • 96:51 - 96:55
    the use of mobile and wireless devices
  • 96:55 - 96:57
    portable and wireless devices present a
  • 96:57 - 96:59
    new threat to an organization's
  • 96:59 - 97:02
    information assets and must be properly
  • 97:02 - 97:05
    controlled policies and procedures as
  • 97:05 - 97:07
    well as additional protection mechanisms
  • 97:07 - 97:09
    must be put into place to ensure that
  • 97:09 - 97:12
    data are protected to a greater extent
  • 97:12 - 97:15
    on portable devices since such devices
  • 97:15 - 97:17
    will most likely operate in environments
  • 97:17 - 97:21
    where physical controls are lacking or
  • 97:21 - 97:23
    non-existent most transportable media
  • 97:23 - 97:25
    including including pdas Blackberry
  • 97:25 - 97:29
    devices Etc are easily lost or stolen
  • 97:29 - 97:31
    and thus require the use of encryption
  • 97:31 - 97:33
    Technologies as well as strong
  • 97:33 - 97:36
    authentication it also may be necessary
  • 97:36 - 97:39
    to classify some data as inappropriate
  • 97:39 - 97:42
    for storage on a mobile device the is
  • 97:42 - 97:44
    auditor should understand that all such
  • 97:44 - 97:46
    media and devices which may include
  • 97:46 - 97:49
    personal music MP3 devices can also be
  • 97:49 - 97:52
    used by an individual to steal both data
  • 97:52 - 97:55
    and programs for personal use or gain we
  • 97:55 - 97:58
    will focus on mobile Computing main
  • 97:58 - 98:01
    areas covered here are mobile Computing
  • 98:01 - 98:04
    in the next screen we will discuss about
  • 98:04 - 98:07
    the risk of using laptops is the
  • 98:07 - 98:08
    difficulty to implement logical and
  • 98:08 - 98:10
    physical security in a mobile
  • 98:10 - 98:14
    environment laptop security controls
  • 98:14 - 98:17
    laptop security measures engraving the
  • 98:17 - 98:20
    serial number company name cable locks
  • 98:20 - 98:23
    monitor detectors regular backup of
  • 98:23 - 98:27
    sensitive data encryption of data
  • 98:27 - 98:30
    allocating passwords to individual files
  • 98:30 - 98:31
    theft response
  • 98:31 - 98:34
    procedures you will now attempt a
  • 98:34 - 98:36
    question to test what you have learned
  • 98:36 - 98:38
    so far in this topic we will learn about
  • 98:38 - 98:40
    the concepts in knowledge statement
  • 98:40 - 98:43
    5.16 let us discuss about voice
  • 98:43 - 98:46
    communication Security in the next
  • 98:46 - 98:49
    screen it is key to no voice
  • 98:49 - 98:52
    communication security for example PBX
  • 98:52 - 98:55
    VoIP the incre increasing complexity and
  • 98:55 - 98:57
    convergence of voice and data
  • 98:57 - 98:59
    Communications introduces additional
  • 98:59 - 99:02
    risks that must be taken into account by
  • 99:02 - 99:06
    the is auditor VoIP and PBX environments
  • 99:06 - 99:09
    involve many security risks both within
  • 99:09 - 99:11
    and outside the organization that must
  • 99:11 - 99:14
    be addressed to ensure the security and
  • 99:14 - 99:16
    reliability of voice
  • 99:16 - 99:18
    Communications main areas to be covered
  • 99:18 - 99:22
    here are Voiceover IP private Branch
  • 99:22 - 99:25
    Exchange in the next slide we will
  • 99:25 - 99:26
    discuss about
  • 99:26 - 99:30
    VoIP IP telepon internet telepon is the
  • 99:30 - 99:32
    technology that makes it possible to
  • 99:32 - 99:35
    have a voice conversation over the
  • 99:35 - 99:37
    Internet protocols used to carry the
  • 99:37 - 99:40
    signal over the IP network are referred
  • 99:40 - 99:43
    to as VoIP VoIP is a technology where
  • 99:43 - 99:45
    voice traffic is carried on top of
  • 99:45 - 99:47
    existing data
  • 99:47 - 99:49
    infrastructure in VoIP sounds are
  • 99:49 - 99:51
    digitized into IP packets and
  • 99:51 - 99:53
    transferred through the network layer
  • 99:53 - 99:55
    before being decoded back into the
  • 99:55 - 99:58
    original voice VoIP has reduced
  • 99:58 - 100:01
    long-distance call costs in a number of
  • 100:01 - 100:03
    organizations thus we will focus on
  • 100:03 - 100:06
    voice over IP and private Branch
  • 100:06 - 100:09
    exchange let us continue to discuss VoIP
  • 100:09 - 100:13
    in the next slide VoIP advantages over
  • 100:13 - 100:16
    traditional telepon VoIP Innovation
  • 100:16 - 100:18
    progresses at Market rates rather than
  • 100:18 - 100:21
    at the rates of itu international
  • 100:21 - 100:24
    telecommunications Union lower costs per
  • 100:24 - 100:27
    call or even free calls for longdistance
  • 100:27 - 100:30
    calls lower infrastructure costs the
  • 100:30 - 100:34
    risk associated with the use of VoIP are
  • 100:34 - 100:36
    the need to protect two assets the data
  • 100:36 - 100:40
    and the voice inherent or security the
  • 100:40 - 100:42
    current Internet architecture does not
  • 100:42 - 100:44
    provide the same physical wire security
  • 100:44 - 100:47
    as the phone lines controls for securing
  • 100:47 - 100:50
    vo is implementing security mechanisms
  • 100:50 - 100:53
    such as those deployed in data networks
  • 100:53 - 100:56
    for for example firewalls encryption to
  • 100:56 - 100:58
    emulate the security level currently
  • 100:58 - 101:02
    used by pstn Network users in the next
  • 101:02 - 101:04
    screen we will discuss about private
  • 101:04 - 101:06
    Branch exchange
  • 101:06 - 101:10
    PBX PBX is a sophisticated
  • 101:10 - 101:11
    computer-based phone system from the
  • 101:11 - 101:13
    early
  • 101:13 - 101:16
    1920s originally it was analog but is
  • 101:16 - 101:19
    now digital principal purpose was to
  • 101:19 - 101:21
    save the cost of providing each person
  • 101:21 - 101:24
    with a line attributes incl include
  • 101:24 - 101:27
    multiple telephone lines digital phones
  • 101:27 - 101:30
    for both voice and data switching calls
  • 101:30 - 101:33
    within pvx non-blocking configuration
  • 101:33 - 101:36
    that allows simultaneous calls operator
  • 101:36 - 101:38
    console or
  • 101:38 - 101:41
    switchboard let us continue discussing
  • 101:41 - 101:45
    private Branch exchange PBX in the next
  • 101:45 - 101:48
    screen the risks associated with use of
  • 101:48 - 101:52
    PBX are theft of service and toll fraud
  • 101:52 - 101:54
    disclosure of information through
  • 101:54 - 101:57
    eavesdropping unauthorized access to
  • 101:57 - 102:00
    resources denial of service traffic
  • 102:00 - 102:03
    analysis passive attack you will now
  • 102:03 - 102:05
    attempt a question to test what you have
  • 102:05 - 102:07
    learned so far in this topic we will
  • 102:07 - 102:09
    learn about the concepts in knowledge
  • 102:09 - 102:11
    statement
  • 102:11 - 102:13
    5.17 let us discuss about evidence
  • 102:13 - 102:16
    preservation techniques in the next
  • 102:16 - 102:18
    screen cea candidate must have a
  • 102:18 - 102:20
    knowledge of the evidence preservation
  • 102:20 - 102:23
    techniques and processes followed in
  • 102:23 - 102:24
    forensic
  • 102:24 - 102:27
    investigations for example it process
  • 102:27 - 102:30
    chain of custody audit conclusions
  • 102:30 - 102:32
    should be supported by reliable and
  • 102:32 - 102:35
    relevant evidence evidence is collected
  • 102:35 - 102:37
    during the course of an audit follows a
  • 102:37 - 102:40
    life cycle the life cycle introduces
  • 102:40 - 102:42
    collection analysis and preservation and
  • 102:42 - 102:45
    destruction of evidence the source of
  • 102:45 - 102:47
    evidence should be reliable and
  • 102:47 - 102:50
    qualified that is from an appropriate
  • 102:50 - 102:52
    original Source rather than obtained as
  • 102:52 - 102:56
    a common or hearsay evidence should
  • 102:56 - 102:58
    originate directly from a trusted source
  • 102:58 - 103:01
    to help ensure objectivity in fraud
  • 103:01 - 103:03
    investigations or legal proceedings
  • 103:03 - 103:05
    maintaining the Integrity of evidence
  • 103:05 - 103:07
    throughout the evidence life cycle may
  • 103:07 - 103:10
    be referred to as the chain of custody
  • 103:10 - 103:12
    when the evidence is classified as
  • 103:12 - 103:15
    forensic audit evidence should include
  • 103:15 - 103:17
    information regarding date of
  • 103:17 - 103:20
    creation main areas covered here are
  • 103:20 - 103:23
    evidence audit documentation
  • 103:23 - 103:26
    investigation techniques continuous
  • 103:26 - 103:29
    auditing in the next few screens we will
  • 103:29 - 103:32
    discuss about investigation
  • 103:32 - 103:34
    techniques investigation techniques
  • 103:34 - 103:37
    include the investigation of computer
  • 103:37 - 103:39
    crime and the protection of evidence and
  • 103:39 - 103:42
    chain of custody among others
  • 103:42 - 103:46
    investigation of computer crime computer
  • 103:46 - 103:49
    crimes are not reported in most cases
  • 103:49 - 103:51
    simply because they are not detected or
  • 103:51 - 103:54
    of the negative publicity they generate
  • 103:54 - 103:56
    in many countries laws are directed
  • 103:56 - 103:58
    toward protecting physical property
  • 103:58 - 104:00
    making it very difficult to use such
  • 104:00 - 104:03
    laws against computer crime it is very
  • 104:03 - 104:05
    important that proper procedures are
  • 104:05 - 104:08
    used to collect evidence from a crime
  • 104:08 - 104:11
    scene the environment and evidence must
  • 104:11 - 104:14
    be left unaltered and specialist law
  • 104:14 - 104:16
    enforcement officials must be called in
  • 104:16 - 104:18
    after a
  • 104:18 - 104:21
    crime computer forensics is the process
  • 104:21 - 104:24
    of identifying preserving and analyzing
  • 104:24 - 104:26
    and presenting digital evidence in a
  • 104:26 - 104:29
    manner that is legally acceptable in any
  • 104:29 - 104:32
    legal proceedings for example Court
  • 104:32 - 104:34
    includes activities involving
  • 104:34 - 104:36
    exploration and application of methods
  • 104:36 - 104:39
    to gather process interpret and use
  • 104:39 - 104:42
    digital evidence loss of preservation of
  • 104:42 - 104:45
    Integrity of evidence means loss of
  • 104:45 - 104:48
    value in legal proceedings the chain of
  • 104:48 - 104:51
    evidence contains information regarding
  • 104:51 - 104:53
    who had access to the evidence cross
  • 104:53 - 104:56
    chronological manner procedures followed
  • 104:56 - 104:58
    in working with the evidence proving
  • 104:58 - 105:01
    analysis is based on copies identical to
  • 105:01 - 105:03
    original
  • 105:03 - 105:06
    evidence considerations regarding
  • 105:06 - 105:10
    evidence identify identify information
  • 105:10 - 105:13
    that may form evidence preserve practice
  • 105:13 - 105:16
    of retrieving identified information and
  • 105:16 - 105:19
    preserving it as evidence involves
  • 105:19 - 105:22
    Imaging of original data and documenting
  • 105:22 - 105:26
    chain of custody analyze involves
  • 105:26 - 105:29
    extracting processing and interpreting
  • 105:29 - 105:32
    the evidence analysis performed on image
  • 105:32 - 105:34
    of the media not the
  • 105:34 - 105:38
    original present involves a presentation
  • 105:38 - 105:40
    to the various audiences such as
  • 105:40 - 105:43
    management attorneys presenter to be
  • 105:43 - 105:45
    qualified and the process of
  • 105:45 - 105:48
    preservation and Analysis
  • 105:48 - 105:51
    credible key elements of computer
  • 105:51 - 105:54
    forensics the is auditor should consider
  • 105:54 - 105:57
    data protection measures to ensure
  • 105:57 - 105:59
    sought-after information isn't altered
  • 105:59 - 106:02
    data acquisition all required data
  • 106:02 - 106:04
    transferred to controlled location and
  • 106:04 - 106:08
    writable media right protected Imaging
  • 106:08 - 106:10
    process allowing for bit forbit
  • 106:10 - 106:13
    replication of data on disk that avoids
  • 106:13 - 106:17
    damage to original data extraction
  • 106:17 - 106:20
    process of identification and selection
  • 106:20 - 106:22
    of relevant data from the imaged data
  • 106:22 - 106:24
    set
  • 106:24 - 106:26
    interrogation used to obtain prior
  • 106:26 - 106:29
    indicators or relationships from
  • 106:29 - 106:32
    extracted data ingestion
  • 106:32 - 106:35
    normalization process of converting
  • 106:35 - 106:37
    extracted information to a format that
  • 106:37 - 106:39
    can be understood by
  • 106:39 - 106:42
    investigators reporting information
  • 106:42 - 106:45
    should be collected and reported in a
  • 106:45 - 106:48
    proper way for it to be valuable you
  • 106:48 - 106:50
    will now attempt a question to test what
  • 106:50 - 106:52
    you have learned so far in this topic we
  • 106:52 - 106:54
    will learn about the concepts in
  • 106:54 - 106:57
    knowledge statement 5.18 let us discuss
  • 106:57 - 107:00
    about data classification standards and
  • 107:00 - 107:03
    supporting procedures in the next screen
  • 107:03 - 107:06
    cesa candidate must have a knowledge of
  • 107:06 - 107:08
    data classification standards and
  • 107:08 - 107:09
    supporting
  • 107:09 - 107:11
    procedures information assets have
  • 107:11 - 107:14
    varying degrees of sensitivity and
  • 107:14 - 107:16
    criticality in meeting business
  • 107:16 - 107:19
    objectives data is classified and
  • 107:19 - 107:22
    protected according to the set degree an
  • 107:22 - 107:24
    important first step to data
  • 107:24 - 107:26
    classification is Discovery inventory
  • 107:26 - 107:29
    and risk assessment once this is
  • 107:29 - 107:31
    accomplished data classification can
  • 107:31 - 107:34
    then be put into use by assigning
  • 107:34 - 107:37
    classes or levels of sensitivity and
  • 107:37 - 107:40
    criticality to information resources and
  • 107:40 - 107:43
    establishing specific security rules for
  • 107:43 - 107:46
    each class Enterprises can Define the
  • 107:46 - 107:48
    level of access controls and the
  • 107:48 - 107:50
    retention time and destruction
  • 107:50 - 107:52
    requirements that should be applied to
  • 107:52 - 107:56
    each information asset the is auditor
  • 107:56 - 107:57
    should understand the process of
  • 107:57 - 108:00
    classification and the interrelationship
  • 108:00 - 108:02
    between data classification and the need
  • 108:02 - 108:05
    for inventorying information assets and
  • 108:05 - 108:08
    assigning responsibility to data owners
  • 108:08 - 108:10
    data owner responsibilities should be
  • 108:10 - 108:14
    clearly identified documented and
  • 108:14 - 108:17
    implemented main areas to be covered
  • 108:17 - 108:20
    here are inventory and classification of
  • 108:20 - 108:24
    information assets in the next screens
  • 108:24 - 108:26
    we will learn about inventory and
  • 108:26 - 108:29
    classification of information assets a
  • 108:29 - 108:32
    detailed inventory of information assets
  • 108:32 - 108:35
    is required for Effective control the
  • 108:35 - 108:37
    inventory is the first step in
  • 108:37 - 108:39
    classifying the assets and determining
  • 108:39 - 108:42
    level of protection required inventory
  • 108:42 - 108:45
    record should include specific
  • 108:45 - 108:48
    identification of the asset relative
  • 108:48 - 108:51
    value to the organization location
  • 108:51 - 108:55
    security risk classific ification asset
  • 108:55 - 108:57
    group where the asset forms part of a
  • 108:57 - 109:02
    larger is owner designated
  • 109:02 - 109:04
    custodian classification should be
  • 109:04 - 109:06
    simple and employed during risk
  • 109:06 - 109:09
    assessment by end user managers and
  • 109:09 - 109:13
    system admins use ISO IEC
  • 109:13 - 109:14
    27012
  • 109:14 - 109:18
    2005 reduce risk and cost of over or
  • 109:18 - 109:21
    under protection used to identify who
  • 109:21 - 109:25
    has access to what who determines access
  • 109:25 - 109:28
    rights and levels approvals required for
  • 109:28 - 109:31
    Access classification done by differing
  • 109:31 - 109:34
    degrees for data sensitivity and mission
  • 109:34 - 109:36
    criticality of the business
  • 109:36 - 109:39
    applications let us continue discussing
  • 109:39 - 109:41
    inventory and classification of
  • 109:41 - 109:43
    information Assets in the next
  • 109:43 - 109:47
    screen classification of assets
  • 109:47 - 109:49
    information assets have varying degrees
  • 109:49 - 109:52
    of sensitivity criticality which
  • 109:52 - 109:55
    determine appropriate levels of control
  • 109:55 - 109:57
    application database criticality
  • 109:57 - 109:59
    classification for example Mission
  • 109:59 - 110:03
    critical significant moderate or low you
  • 110:03 - 110:05
    will now attempt a question to test what
  • 110:05 - 110:07
    you have learned so far in this topic we
  • 110:07 - 110:09
    will learn about the concepts in
  • 110:09 - 110:11
    knowledge statement
  • 110:11 - 110:13
    5.19 let us discuss about physical
  • 110:13 - 110:16
    access controls in the next screen
  • 110:16 - 110:18
    candidates should know of physical
  • 110:18 - 110:21
    access controls for the identification
  • 110:21 - 110:23
    authentication and restriction of users
  • 110:23 - 110:26
    to authorized facilities physical
  • 110:26 - 110:29
    security weaknesses can result in
  • 110:29 - 110:32
    financial loss legal repercussions loss
  • 110:32 - 110:34
    of credibility or loss of Competitive
  • 110:34 - 110:38
    Edge thus information assets must be
  • 110:38 - 110:40
    protected against physical attacks such
  • 110:40 - 110:43
    as vandalism and theft through controls
  • 110:43 - 110:45
    that restrict access to sensitive areas
  • 110:45 - 110:47
    containing computer equipment or
  • 110:47 - 110:51
    confidential data files such controls
  • 110:51 - 110:53
    usually employ the use of a access door
  • 110:53 - 110:56
    locks that require the use of a password
  • 110:56 - 110:59
    key token or biometric authentication of
  • 110:59 - 111:02
    the person attempting entry in high
  • 111:02 - 111:05
    security areas access may require
  • 111:05 - 111:07
    authentication through multiple means
  • 111:07 - 111:10
    and the use of strong security measures
  • 111:10 - 111:13
    such as the airlock type or Man Trap
  • 111:13 - 111:16
    entrances the is auditor should
  • 111:16 - 111:18
    understand the nature of physical
  • 111:18 - 111:20
    controls and the ways in which they can
  • 111:20 - 111:23
    be circumvented as well as the con
  • 111:23 - 111:25
    concept of the security boundary to
  • 111:25 - 111:27
    establish where such devices should be
  • 111:27 - 111:31
    placed and how effective they must be
  • 111:31 - 111:33
    main areas covered here are physical
  • 111:33 - 111:37
    access controls and exposures physical
  • 111:37 - 111:40
    access controls and exposures is our
  • 111:40 - 111:42
    main focus in the next
  • 111:42 - 111:45
    screen physical access controls door
  • 111:45 - 111:48
    locks bolting combination electronic
  • 111:48 - 111:52
    biometric dead man doors logging manual
  • 111:52 - 111:56
    elect ronic identification badges video
  • 111:56 - 112:00
    cameras security guards controlled
  • 112:00 - 112:04
    visitor access bonded Personnel not
  • 112:04 - 112:06
    advertising locations of sensitive
  • 112:06 - 112:10
    facilities computer workstation locks
  • 112:10 - 112:13
    controlled single entry points alarm
  • 112:13 - 112:16
    systems secured report documentation
  • 112:16 - 112:19
    distribution cards primarily originate
  • 112:19 - 112:23
    from natural and man-made hazards Expos
  • 112:23 - 112:26
    ures include unauthorized entry damage
  • 112:26 - 112:30
    vandalism theft viewing or copying
  • 112:30 - 112:34
    sensitive information alteration of data
  • 112:34 - 112:36
    public disclosure of sensitive
  • 112:36 - 112:39
    information abuse of processing
  • 112:39 - 112:41
    facilities blackmail and
  • 112:41 - 112:44
    embezzlement let us continue discussing
  • 112:44 - 112:47
    physical access exposures in the next
  • 112:47 - 112:51
    screen auditing physical access involves
  • 112:51 - 112:53
    during the information process ing
  • 112:53 - 112:56
    facility visibly observing physical
  • 112:56 - 112:58
    access controls reviewing physical
  • 112:58 - 113:00
    security
  • 113:00 - 113:02
    documentation evaluating General
  • 113:02 - 113:05
    cleanliness doors windows walls curtains
  • 113:05 - 113:08
    ceilings raised floors and
  • 113:08 - 113:10
    ventilation you will now attempt a
  • 113:10 - 113:12
    question to test what you have learned
  • 113:12 - 113:15
    so far in this topic we will learn about
  • 113:15 - 113:17
    the concepts in knowledge statement
  • 113:17 - 113:21
    5.20 let us discuss about Environmental
  • 113:21 - 113:23
    Protection devices and supporting
  • 113:23 - 113:26
    practices in the next screen cea
  • 113:26 - 113:28
    candidate has to have a knowledge of
  • 113:28 - 113:31
    Environmental Protection devices and
  • 113:31 - 113:34
    supporting practices certain natural and
  • 113:34 - 113:37
    man-made events have the ability to do
  • 113:37 - 113:39
    great damage to an organization's
  • 113:39 - 113:41
    information systems and business
  • 113:41 - 113:44
    processes most data centers have
  • 113:44 - 113:46
    mechanisms to prevent detect or mitigate
  • 113:46 - 113:49
    the impact of these threats however it
  • 113:49 - 113:51
    is important that the Readiness and
  • 113:51 - 113:54
    sufficiency of these controls be
  • 113:54 - 113:56
    periodically tested by management to
  • 113:56 - 113:59
    ensure that they will function as
  • 113:59 - 114:01
    intended the is auditor should
  • 114:01 - 114:03
    understand the nature of these controls
  • 114:03 - 114:05
    and how to ensure that they are
  • 114:05 - 114:08
    functioning properly and are adequate to
  • 114:08 - 114:09
    protect the
  • 114:09 - 114:12
    organization let us continue discussing
  • 114:12 - 114:14
    about Environmental Protection devices
  • 114:14 - 114:16
    and supporting
  • 114:16 - 114:18
    practices environmental controls
  • 114:18 - 114:20
    generally include fire and smoke
  • 114:20 - 114:23
    detectors fire suppression systems water
  • 114:23 - 114:26
    detectors and temperature and humidity
  • 114:26 - 114:29
    controls the is auditor should know the
  • 114:29 - 114:31
    relative merits of different fire
  • 114:31 - 114:33
    suppression systems and in what
  • 114:33 - 114:35
    circumstances one type is more
  • 114:35 - 114:38
    appropriate than another main areas of
  • 114:38 - 114:41
    coverage are environmental exposures and
  • 114:41 - 114:44
    controls in the next few screens we will
  • 114:44 - 114:46
    discuss about environmental exposures
  • 114:46 - 114:47
    and
  • 114:47 - 114:50
    controls the environmental exposures
  • 114:50 - 114:53
    include natural events like lightning
  • 114:53 - 114:57
    storms earthquakes Etc power failures is
  • 114:57 - 115:00
    of particular concern total failure
  • 115:00 - 115:04
    blackouts severely reduced voltage
  • 115:04 - 115:08
    brownouts sags spikes and surges
  • 115:08 - 115:11
    electromagnetic interference Emi caused
  • 115:11 - 115:15
    by electrical storms or noisy electrical
  • 115:15 - 115:18
    equipment static electricity magnetic
  • 115:18 - 115:22
    fields water damage and flooding Fire
  • 115:22 - 115:27
    Man and terrorism vandalism smoke food
  • 115:27 - 115:31
    natural elements humidity dust
  • 115:31 - 115:35
    temperature environmental controls power
  • 115:35 - 115:38
    continuity power generators long-term
  • 115:38 - 115:41
    power interruptions surge protectors at
  • 115:41 - 115:44
    least on all expensive equipment UPS
  • 115:44 - 115:49
    devices sags spikes surges emergency
  • 115:49 - 115:52
    power off switch redundant power lines
  • 115:52 - 115:55
    for example leads from two
  • 115:55 - 115:58
    substations fire controls fire
  • 115:58 - 116:00
    extinguishers strategically plac
  • 116:00 - 116:03
    throughout facility fire suppression
  • 116:03 - 116:05
    systems either waterbased sprinklers
  • 116:05 - 116:09
    damages equipment or dry pipe sprinklers
  • 116:09 - 116:12
    Halon systems or CO2 based regular
  • 116:12 - 116:15
    inspection by the fire department also
  • 116:15 - 116:18
    use of audible fire alarms smoke
  • 116:18 - 116:20
    detectors having defined
  • 116:20 - 116:22
    responsibilities marked locations
  • 116:22 - 116:25
    fireproof walls floors and
  • 116:25 - 116:28
    ceilings more however environmental
  • 116:28 - 116:30
    controls that can be applied are
  • 116:30 - 116:33
    strategically locating the computer room
  • 116:33 - 116:36
    not basement raised floors and water
  • 116:36 - 116:40
    detectors water proper ventilation
  • 116:40 - 116:43
    humidity and temperature control wiring
  • 116:43 - 116:46
    placed in fire resistant panels and
  • 116:46 - 116:48
    conduits prohibit eating drinking and
  • 116:48 - 116:51
    smoking within information processing
  • 116:51 - 116:54
    facilities documented and tested
  • 116:54 - 116:57
    emergency evacuation plan auditing
  • 116:57 - 117:00
    environmental controls involve checking
  • 117:00 - 117:03
    that systems work as specified and are
  • 117:03 - 117:05
    inspected and tested at least once a
  • 117:05 - 117:07
    year placing and assigning
  • 117:07 - 117:10
    responsibility to concerned persons
  • 117:10 - 117:13
    maintaining communication and awareness
  • 117:13 - 117:15
    having a business continuity plan that
  • 117:15 - 117:18
    will be used in case of a disaster this
  • 117:18 - 117:21
    plan should be fully documented and
  • 117:21 - 117:24
    tested you will now attempt a question
  • 117:24 - 117:26
    to test what you have learned so far in
  • 117:26 - 117:28
    this topic we will learn about the
  • 117:28 - 117:31
    concepts in knowledge statement
  • 117:31 - 117:34
    5.21 let us discuss about handling
  • 117:34 - 117:36
    confidential information Assets in the
  • 117:36 - 117:37
    next few
  • 117:37 - 117:40
    screens knowledge of the processes and
  • 117:40 - 117:43
    procedures used to store retrieve
  • 117:43 - 117:45
    transport and disposal of confidential
  • 117:45 - 117:48
    information assets is key for a cesa
  • 117:48 - 117:50
    candidate to learn confidential
  • 117:50 - 117:53
    information assets are vulnerable during
  • 117:53 - 117:56
    storage retrieval and transport and must
  • 117:56 - 117:59
    be disposed of properly management
  • 117:59 - 118:01
    should Define and Implement procedures
  • 118:01 - 118:04
    to prevent unauthorized access to or
  • 118:04 - 118:06
    loss of sensitive information and
  • 118:06 - 118:09
    software from computers Diss and other
  • 118:09 - 118:12
    equipment or media when they are stored
  • 118:12 - 118:14
    transported or transmitted during
  • 118:14 - 118:18
    processing retrieval and output the is
  • 118:18 - 118:20
    auditor should also understand the need
  • 118:20 - 118:22
    for correct disposal of information and
  • 118:22 - 118:25
    media in order to ensure that no
  • 118:25 - 118:27
    unauthorized person gain access to the
  • 118:27 - 118:30
    information by restoration or
  • 118:30 - 118:32
    Recreation thus we will mainly discuss
  • 118:32 - 118:35
    about storing retrieving transport and
  • 118:35 - 118:38
    disposing of confidential information
  • 118:38 - 118:41
    Assets in the next slide let us discuss
  • 118:41 - 118:44
    about handling confidential information
  • 118:44 - 118:47
    storing retrieving transporting and
  • 118:47 - 118:49
    disposing of confidential information
  • 118:49 - 118:52
    need procedures to prevent access to or
  • 118:52 - 118:54
    loss of sensitive information and
  • 118:54 - 118:57
    software further controls are required
  • 118:57 - 119:01
    for backup files and databases data
  • 119:01 - 119:04
    banks disposal of media previously used
  • 119:04 - 119:06
    to hold confidential information
  • 119:06 - 119:08
    management of equipment sent for
  • 119:08 - 119:11
    off-site maintenance public agencies and
  • 119:11 - 119:14
    organizations concerned with sensitive
  • 119:14 - 119:17
    critical or confidential information e
  • 119:17 - 119:21
    toen electronic Keys storage records let
  • 119:21 - 119:23
    us continue discussing handling
  • 119:23 - 119:25
    confidential information in the next
  • 119:25 - 119:28
    screen preserving information during
  • 119:28 - 119:30
    shipment or storage by keeping out of
  • 119:30 - 119:33
    direct sunlight keeping free of dust
  • 119:33 - 119:35
    keep free of liquids minimize exposure
  • 119:35 - 119:38
    to magnetic fields radio equipment or
  • 119:38 - 119:41
    any sources of vibration do not Air
  • 119:41 - 119:43
    transport in areas and at times of
  • 119:43 - 119:46
    exposure to a strong magnetic storm you
  • 119:46 - 119:48
    will now attempt a question to test what
  • 119:48 - 119:51
    you have learned so far protection of
  • 119:51 - 119:53
    information assets
  • 119:53 - 119:57
    one a long asymmetric encryption key
  • 119:57 - 119:59
    public key encryption increases
  • 119:59 - 120:03
    encryption overhead cost two creating
  • 120:03 - 120:05
    user accounts that automatically expire
  • 120:05 - 120:08
    by predetermined date is an effective
  • 120:08 - 120:11
    control for granting temporary access to
  • 120:11 - 120:14
    vendors and external support Personnel
  • 120:14 - 120:18
    three worms are malicious programs that
  • 120:18 - 120:21
    can run independently and can propagate
  • 120:21 - 120:23
    without the aid of a carrier program
  • 120:23 - 120:28
    such as email four identifying Network
  • 120:28 - 120:31
    applications such as mail web of FTP
  • 120:31 - 120:34
    servers to be externally accessed is an
  • 120:34 - 120:36
    initial step in creating a proper
  • 120:36 - 120:38
    firewall
  • 120:38 - 120:42
    policy five SSL protocol provides
  • 120:42 - 120:44
    confidentiality through symmetric
  • 120:44 - 120:47
    encryption such as data encryption
  • 120:47 - 120:51
    standard six intrusion detection systems
  • 120:51 - 120:54
    IDs are used to gather evidence of
  • 120:54 - 120:58
    network attacks seven time stamps are an
  • 120:58 - 121:00
    effective control for detecting
  • 121:00 - 121:03
    duplicate transactions such as payment
  • 121:03 - 121:07
    made or received eight traffic analysis
  • 121:07 - 121:09
    is a passive attack method used by
  • 121:09 - 121:12
    Intruders to determine potential Network
  • 121:12 - 121:16
    attacks nine file encryption is a good
  • 121:16 - 121:18
    control for protecting confidential data
  • 121:18 - 121:23
    that resides on a PC 10 although many
  • 121:23 - 121:26
    methods of fire suppression exist dry
  • 121:26 - 121:28
    pipe sprinklers are considered to be the
  • 121:28 - 121:32
    most environmentally friendly 11 logical
  • 121:32 - 121:35
    access controls should be reviewed to
  • 121:35 - 121:37
    ensure that access is granted on a least
  • 121:37 - 121:40
    privilege basis for the organization's
  • 121:40 - 121:44
    data owners 12 a callback system is a
  • 121:44 - 121:47
    remote access control in which the user
  • 121:47 - 121:48
    initially connects to the network
  • 121:48 - 121:52
    systems via dialup access only to have
  • 121:52 - 121:54
    the connection terminated by the server
  • 121:54 - 121:57
    which then subsequently dials back the
  • 121:57 - 121:59
    user at a predetermined number stored in
  • 121:59 - 122:03
    the server's configuration database 13
  • 122:03 - 122:05
    information system security policies are
  • 122:05 - 122:07
    used as the framework for developing
  • 122:07 - 122:09
    logical
  • 122:09 - 122:12
    access this concludes the domain on
  • 122:12 - 122:15
    protection of information assets this is
  • 122:15 - 122:17
    the last domain to be covered in this
  • 122:17 - 122:20
    course with this we've come to the end
  • 122:20 - 122:24
    of this course happy learning
Title:
Protection Of Information Assets | CISA Training Videos
Description:

more » « less
Video Language:
English
Duration:
02:02:23

English subtitles

Revisions Compare revisions