You are on page 1of 67

CISSP Passport 1st Edition Bobby E.

Rogers
Visit to download the full and correct content document:
https://ebookmass.com/product/cissp-passport-1st-edition-bobby-e-rogers/
Mike Meyers’

A+
CISSP
CompTIA ® ®

CERTIFICATION
PASSPORT
PASSPORT SEVENTH
(Exams 220-1001 & 220-1002) EDITION
About the Author

Bobby Rogers (he/his/him) is a cybersecurity proessional with over 30 years in the inor-
mation technology and cybersecurity ields. He currently works with a major engineering
company in Huntsville, Alabama, helping to secure networks and manage cyber risk or its
customers. Bobby’s customers include the U.S. Army, NASA, the State o ennessee, and
private/commercial companies and organizations. His specialties are cybersecurity engineer-
ing, security compliance, and cyber risk management, but he has worked in almost every area
o cybersecurity, including network deense, computer orensics and incident response, and
penetration testing.
Bobby is a retired Master Sergeant rom the U.S. Air Force, having served or over 21 years.
He has built and secured networks in the United States, Chad, Uganda, South Arica, Germany,
Saudi Arabia, Pakistan, Aghanistan, and several other remote locations. His decorations
include two Meritorious Service medals, three Air Force Commendation medals, the National
Deense Service medal, and several Air Force Achievement medals. He retired rom active
duty in 2006.
Bobby has a master o science in inormation assurance and a bachelor o science in
computer inormation systems (with a dual concentration in Russian language), and two
associate o science degrees. His many certiications include CISSP-ISSEP, CRISC, CySA+,
CEH, and MCSE: Security.
Bobby has narrated and produced over 30 computer training videos or several training
companies and currently produces them or Pluralsight (https://www.pluralsight.com). He
is also the author o CompTIA Mobility+ All-in-One Exam Guide (Exam MB0-001), CRISC
Certiied in Risk and Inormation Systems Control All-in-One Exam Guide, and Mike Meyers’
CompTIA Security+ Certiication Guide (Exam SY0-401), and is the contributing author/
technical editor or the popular CISSP All-in-One Exam Guide, Ninth Edition, all o which are
published by McGraw Hill.

About the Technical Editor


Nichole O’Brien is a creative business leader with over 25 years o experience in cybersecurity
and I leadership, program management, and business development across commercial,
education, and ederal, state, and local business markets. Her ocus on innovative solutions is
demonstrated by the development o a commercial cybersecurity and I business group, which
she currently manages in a Fortune 500 corporation and has received the corporation’s annual
Outstanding Customer Service Award. She currently serves as Vice President o Outreach or
Cyber Huntsville, is on the Foundation Board or the National Cyber Summit, and supports
cyber education initiatives like the USSRC Cyber Camp. Nichole has bachelor’s and master’s
degrees in business administration and has a CISSP certiication.
Mike Meyers’

A+
CISSP
CompTIA ® ®

CERTIFICATION
PASSPORT
PASSPORT SEVENTH
(Exams 220-1001 & 220-1002) EDITION

Bobby E. Rogers

New York Chicago San Francisco Athens


London Madrid Mexico City Milan
New Delhi Singapore Sydney Toronto

McGraw Hill is an independent entity rom (ISC)²® and is not afliated with (ISC)² in any manner. Tis study/training guide and/or material is not
sponsored by, endorsed by, or afliated with (ISC)2 in any manner. Tis publication and accompanying media may be used in assisting students to
prepare or the CISSP exam. Neither (ISC)² nor McGraw Hill warrants that use o this publication and accompanying media will ensure passing any
exam. (ISC)²®, CISSP®, CAP®, ISSAP®, ISSEP®, ISSMP®, SSCP®, and CBK® are trademarks or registered trademarks o (ISC)² in the United States and
certain other countries. All other trademarks are trademarks o their respective owners.
Copyright © 2023 by McGraw Hill. All rights reserved. Except as permitted under the United States Copyright Act of 1976, no
part of this publication may be reproduced or distributed in any form or by any means, or stored in a database or retrieval system,
without the prior written permission of the publisher, with the exception that the program listings may be entered, stored, and
executed in a computer system, but they may not be reproduced for publication.

ISBN: 978-1-26-427798-8
MHID: 1-26-427798-9

The material in this eBook also appears in the print version of this title: ISBN: 978-1-26-427797-1,
MHID: 1-26-427797-0.

eBook conversion by codeMantra


Version 1.0

All trademarks are trademarks of their respective owners. Rather than put a trademark symbol after every occurrence of a trade-
marked name, we use names in an editorial fashion only, and to the benet of the trademark owner, with no intention of infringe-
ment of the trademark. Where such designations appear in this book, they have been printed with initial caps.

McGraw Hill eBooks are available at special quantity discounts to use as premiums and sales promotions or for use in corporate
training programs. To contact a representative, please visit the Contact Us page at www.mhprofessional.com.

Information has been obtained by McGraw Hill from sources believed to be reliable. However, because of the possibility of hu-
man or mechanical error by our sources, McGraw Hill, or others, McGraw Hill does not guarantee the accuracy, adequacy, or
completeness of any information and is not responsible for any errors or omissions or the results obtained from the use of such
information.

TERMS OF USE

This is a copyrighted work and McGraw-Hill Education and its licensors reserve all rights in and to the work. Use of this work
is subject to these terms. Except as permitted under the Copyright Act of 1976 and the right to store and retrieve one copy of the
work, you may not decompile, disassemble, reverse engineer, reproduce, modify, create derivative works based upon, transmit,
distribute, disseminate, sell, publish or sublicense the work or any part of it without McGraw-Hill Education’s prior consent. You
may use the work for your own noncommercial and personal use; any other use of the work is strictly prohibited. Your right to
use the work may be terminated if you fail to comply with these terms.

THE WORK IS PROVIDED “AS IS.” McGRAW-HILL EDUCATION AND ITS LICENSORS MAKE NO GUARANTEES
OR WARRANTIES AS TO THE ACCURACY, ADEQUACY OR COMPLETENESS OF OR RESULTS TO BE OBTAINED
FROM USING THE WORK, INCLUDING ANY INFORMATION THAT CAN BE ACCESSED THROUGH THE WORK VIA
HYPERLINK OR OTHERWISE, AND EXPRESSLY DISCLAIM ANY WARRANTY, EXPRESS OR IMPLIED, INCLUD-
ING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE. McGraw-Hill Education and its licensors do not warrant or guarantee that the functions contained in the work will
meet your requirements or that its operation will be uninterrupted or error free. Neither McGraw-Hill Education nor its licensors
shall be liable to you or anyone else for any inaccuracy, error or omission, regardless of cause, in the work or for any damages
resulting therefrom. McGraw-Hill Education has no responsibility for the content of any information accessed through the work.
Under no circumstances shall McGraw-Hill Education and/or its licensors be liable for any indirect, incidental, special, punitive,
consequential or similar damages that result from the use of or inability to use the work, even if any of them has been advised of
the possibility of such damages. This limitation of liability shall apply to any claim or cause whatsoever whether such claim or
cause arises in contract, tort or otherwise.
I’d like to dedicate this book to the cybersecurity proessionals who
tirelessly, and sometimes, thanklessly, protect our inormation and
systems rom all who would do them harm.
I also dedicate this book to the people who serve in uniorm as
military personnel, public saety proessionals, police, frefghters,
and medical proessionals, sacrifcing sometimes all that they are
and have so that we may all live in peace, security, and saety.

—Bobby Rogers
This page intentionally left blank
DOMAIN vii

Contents at a Glance

1.0 Security and Risk Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1


2.0 Asset Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
3.0 Security Architecture and Engineering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
4.0 Communication and Network Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
5.0 Identity and Access Management (IAM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
6.0 Security Assessment and esting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
7.0 Security Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
8.0 Sotware Development Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
A About the Online Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431

vii
This page intentionally left blank
DOMAIN ix

Contents

Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvii
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxix

1.0 Security and Risk Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1


Objective 1.1 Understand, adhere to,
and promote professional ethics . . . . . . . . . . . . . . . . . . . . . . . . . . 2
The (ISC)2 Code of Ethics                                              3
Code of Ethics Preamble                                         3
Code of Ethics Canons                                          3
Organizational Code of Ethics                                          4
Workplace Ethics Statements and Policies                          4
Other Sources for Ethics Requirements                             5
REVIEW                                                          7
11 QUESTIONS                                               7
11 ANSWERS                                                8
Objective 1.2 Understand and apply security concepts . . . . . . . . . . . 9
Security Concepts                                                   9
Data, Information, Systems, and Entities                            9
Confidentiality                                                10
Integrity                                                      11
Availability                                                   11
Supporting Tenets of Information Security                                11
Identification                                                  11
Authentication                                                11
Authenticity                                                  12
Authorization                                                 12
Auditing and Accountability                                      12
Nonrepudiation                                                12
Supporting Security Concepts                                    13

ix
x CISSP Passport

REVIEW                                                          14
12 QUESTIONS                                               14
12 ANSWERS                                                15
Objective 1.3 Evaluate and apply security governance principles . . . 16
Security Governance                                                 16
External Governance                                            16
Internal Governance                                            16
Alignment of Security Functions to Business Requirements                  17
Business Strategy and Security Strategy                            17
Organizational Processes                                        18
Organizational Roles and Responsibilities                           18
Security Control Frameworks                                     19
Due Care/Due Diligence                                         20
REVIEW                                                          21
13 QUESTIONS                                               21
13 ANSWERS                                                22
Objective 1.4 Determine compliance and other requirements . . . . . . 23
Compliance                                                        23
Legal and Regulatory Compliance                                 24
Contractual Compliance                                         25
Compliance with Industry Standards                               25
Privacy Requirements                                           25
REVIEW                                                          26
14 QUESTIONS                                               27
14 ANSWERS                                                28
Objective 1.5 Understand legal and regulatory issues that pertain to
information security in a holistic context. . . . . . . . . . . . . . . . . . . . 29
Legal and Regulatory Requirements                                     29
Cybercrimes                                                  29
Licensing and Intellectual Property Requirements                     30
Import/Export Controls                                          31
Transborder Data Flow                                          32
Privacy Issues                                                 32
REVIEW                                                          33
15 QUESTIONS                                               33
15 ANSWERS                                                34
Objective 1.6 Understand requirements for investigation types (i.e.,
administrative, criminal, civil, regulatory, industry standards) . . . 35
Investigations                                                      35
Administrative Investigations                                     35
Civil Investigations                                             35
Contents xi
Criminal Investigations                                          36
Regulatory Investigations                                        36
Industry Standards for Investigations                              37
REVIEW                                                          37
16 QUESTIONS                                               38
16 ANSWERS                                                39
Objective 1.7 Develop, document, and implement security policy,
standards, procedures, and guidelines . . . . . . . . . . . . . . . . . . . . . 39
Internal Governance                                                 40
Policy                                                        40
Procedures                                                   40
Standards                                                    41
Guidelines                                                    41
Baselines                                                    42
REVIEW                                                          42
17 QUESTIONS                                               43
17 ANSWERS                                                44
Objective 1.8 Identify, analyze, and prioritize Business Continuity (BC)
requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Business Continuity                                                  45
Business Impact Analysis                                        46
Developing the BIA                                             46
REVIEW                                                          47
18 QUESTIONS                                               47
18 ANSWERS                                                48
Objective 1.9 Contribute to and enforce personnel security policies
and procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Personnel Security                                                   49
Candidate Screening and Hiring                                   49
Employment Agreements and Policies                              50
Onboarding, Transfers, and Termination Processes                    50
Vendor, Consultant, and Contractor Agreements and Controls           52
Compliance Policy Requirements                                  53
Privacy Policy Requirements                                      53
REVIEW                                                          54
19 QUESTIONS                                               55
19 ANSWERS                                                56
Objective 1.10 Understand and apply risk management concepts . . . 57
Risk Management                                                   57
Elements of Risk                                               57
Identify Threats and Vulnerabilities                                59
xii CISSP Passport

Risk Assessment/Analysis                                       60
Risk Response                                                 63
Risk Frameworks                                               64
Countermeasure Selection and Implementation                      64
Applicable Types of Controls                                     65
Control Assessments (Security and Privacy)                         66
Monitoring and Measurement                                    67
Reporting                                                    67
Continuous Improvement                                        68
REVIEW                                                          68
110 QUESTIONS                                              69
110 ANSWERS                                               69
Objective 1.11 Understand and apply threat modeling concepts and
methodologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Threat Modeling                                                    70
Threat Components                                            70
Threat Modeling Methodologies                                  72
REVIEW                                                          73
111 QUESTIONS                                              73
111 ANSWERS                                               73
Objective 1.12 Apply Supply Chain Risk Management
(SCRM) concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Supply Chain Risk Management                                        74
Risks Associated with Hardware, Software, and Services              74
Third-Party Assessment and Monitoring                            76
Minimum Security Requirements                                  77
Service Level Requirements                                      77
REVIEW                                                          77
112 QUESTIONS                                              78
112 ANSWERS                                               79
Objective 1.13 Establish and maintain a security awareness, education,
and training program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Security Awareness, Education, and Training Program                      80
Methods and Techniques to Present Awareness and Training           80
Periodic Content Reviews                                        82
Program Effectiveness Evaluation                                 82
REVIEW                                                          82
113 QUESTIONS                                              83
113 ANSWERS                                               84
Contents xiii

2.0 Asset Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85


Objective 2.1 Identify and classify information and assets. . . . . . . . . 86
Asset Classification                                                  86
Data Classification                                                  87
REVIEW                                                         
89
21 QUESTIONS                                               89
21 ANSWERS                                                90
Objective 2.2 Establish information and asset handling
requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Information and Asset Handling                                        90
Handling Requirements                                         91
Information Classification and Handling Systems                     93
REVIEW                                                          94
22 QUESTIONS                                               95
22 ANSWERS                                                95
Objective 2.3 Provision resources securely . . . . . . . . . . . . . . . . . . . . . 96
Securing Resources                                                  96
Asset Ownership                                              96
Asset Inventory                                                96
Asset Management                                            97
REVIEW                                                          98
23 QUESTIONS                                               99
23 ANSWERS                                                99
Objective 2.4 Manage data lifecycle . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Managing the Data Life Cycle                                          100
Data Roles                                                   100
Data Collection                                                102
Data Location                                                 102
Data Maintenance                                             102
Data Retention                                                103
Data Remanence                                              103
Data Destruction                                               103
REVIEW                                                          104
24 QUESTIONS                                               104
24 ANSWERS                                                105
Objective 2.5 Ensure appropriate asset retention
(e.g., End-of-Life (EOL), End-of-Support (EOS)). . . . . . . . . . . . . . . 105
Asset Retention                                                     105
Asset Life Cycle                                               106
End-of-Life and End-of-Support                                   106
xiv CISSP Passport

REVIEW                                                          108
25 QUESTIONS                                               108
25 ANSWERS                                                108
Objective 2.6 Determine data security controls and compliance
requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Data Security and Compliance                                         109
Data States                                                   109
Control Standards Selection                                      110
Scoping and Tailoring Data Security Controls                        111
Data Protection Methods                                        111
REVIEW                                                          113
26 QUESTIONS                                               113
26 ANSWERS                                                114
3.0 Security Architecture and Engineering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Objective 3.1 Research, implement, and manage engineering
processes using secure design principles . . . . . . . . . . . . . . . . . . . 116
Threat Modeling                                                    116
Least Privilege                                                      116
Defense in Depth                                                    117
Secure Defaults                                                     117
Fail Securely                                                       117
Separation of Duties                                                 118
Keep It Simple                                                      119
Zero Trust                                                          119
Privacy by Design                                                   119
Trust But Verify                                                     119
Shared Responsibility                                                120
REVIEW                                                          120
31 QUESTIONS                                               121
31 ANSWERS                                                122
Objective 3.2 Understand the fundamental concepts of security
models (e.g., Biba, Star Model, Bell-LaPadula) . . . . . . . . . . . . . . . 122
Security Models                                                    122
Terms and Concepts                                            123
System States and Processing Modes                              124
Confidentiality Models                                          126
Integrity Models                                               127
Other Access Control Models                                     128
REVIEW                                                          128
32 QUESTIONS                                               129
32 ANSWERS                                                130
Contents xv
Objective 3.3 Select controls based upon systems security
requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Selecting Security Controls                                            130
Performance and Functional Requirements                          131
Data Protection Requirements                                    131
Governance Requirements                                       132
Interface Requirements                                         132
Risk Response Requirements                                     133
REVIEW                                                          133
33 QUESTIONS                                               134
33 ANSWERS                                                134
Objective 3.4 Understand security capabilities of Information Systems
(IS) (e.g., memory protection, Trusted Platform Module (TPM),
encryption/decryption) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Information System Security Capabilities                                 135
Hardware and Firmware System Security                           135
Secure Processing                                             137
REVIEW                                                          138
34 QUESTIONS                                               139
34 ANSWERS                                                139
Objective 3.5 Assess and mitigate the vulnerabilities of security
architectures, designs, and solution elements . . . . . . . . . . . . . . . 139
Vulnerabilities of Security Architectures, Designs, and Solutions              140
Client-Based Systems                                           140
Server-Based Systems                                          140
Distributed Systems                                            141
Database Systems                                             141
Cryptographic Systems                                          142
Industrial Control Systems                                       142
Internet of Things                                              143
Embedded Systems                                            143
Cloud-Based Systems                                           144
Virtualized Systems                                            145
Containerization                                               146
Microservices                                                 146
Serverless                                                    146
High-Performance Computing Systems                             146
Edge Computing Systems                                        146
REVIEW                                                          147
35 QUESTIONS                                               148
35 ANSWERS                                                148
xvi CISSP Passport

Objective 3.6 Select and determine cryptographic solutions . . . . . . . 148


Cryptography                                                       149
Cryptographic Life Cycle                                         149
Cryptographic Methods                                         151
Integrity                                                      154
Hybrid Cryptography                                            155
Digital Certificates                                             156
Public Key Infrastructure                                        156
Nonrepudiation and Digital Signatures                             158
Key Management Practices                                      158
REVIEW                                                          159
36 QUESTIONS                                               160
36 ANSWERS                                                161
Objective 3.7 Understand methods of cryptanalytic attacks. . . . . . . . 161
Cryptanalytic Attacks                                                161
Brute Force                                                   162
Ciphertext Only                                                162
Known Plaintext                                               162
Chosen Ciphertext and Chosen Plaintext                            163
Frequency Analysis                                             163
Implementation                                                163
Side Channel                                                  163
Fault Injection                                                 164
Timing                                                       164
Man-in-the-Middle (On-Path)                                     164
Pass the Hash                                                 165
Kerberos Exploitation                                           165
Ransomware                                                  165
REVIEW                                                          166
37 QUESTIONS                                               166
37 ANSWERS                                                167
Objective 3.8 Apply security principles to site and facility design . . . 167
Site and Facility Design                                               167
Site Planning                                                  167
Secure Design Principles                                        168
REVIEW                                                          172
38 QUESTIONS                                               172
38 ANSWERS                                                173
Objective 3.9 Design site and facility security controls . . . . . . . . . . . . 173
Designing Facility Security Controls                                     173
Crime Prevention Through Environmental Design                     174
Key Facility Areas of Concern                                     174
Contents xvii
REVIEW                                                          181
39 QUESTIONS                                               181
39 ANSWERS                                                182
4.0 Communication and Network Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Objective 4.1 Assess and implement secure design principles
in network architectures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Fundamental Networking Concepts                                     184
Open Systems Interconnection and Transmission Control Protocol/Internet
Protocol Models                                             185
Internet Protocol Networking                                     187
Secure Protocols                                               189
Application of Secure Networking Concepts                              193
Implications of Multilayer Protocols                               193
Converged Protocols                                            194
Micro-segmentation                                            195
Wireless Technologies                                               197
Wireless Theory and Signaling                                   197
Wi-Fi                                                        199
Bluetooth                                                    202
Zigbee                                                       202
Satellite                                                     203
Li-Fi                                                         203
Cellular Networks                                              204
Content Distribution Networks                                         205
REVIEW                                                          206
41 QUESTIONS                                               206
41 ANSWERS                                                207
Objective 4.2 Secure network components . . . . . . . . . . . . . . . . . . . . . 207
Network Security Design and Components                               208
Operation of Hardware                                          208
Transmission Media                                            212
Endpoint Security                                              213
REVIEW                                                          214
42 QUESTIONS                                               214
42 ANSWERS                                                214
Objective 4.3 Implement secure communication channels
according to design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Securing Communications Channels                                     215
Voice                                                        215
Multimedia Collaboration                                        218
xviii CISSP Passport

Remote Access                                                219


Data Communications                                          220
Virtualized Networks                                           222
Third-Party Connectivity                                         222
REVIEW                                                          223
43 QUESTIONS                                               223
43 ANSWERS                                                224
5.0 Identity and Access Management (IAM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Objective 5.1 Control physical and logical access to assets . . . . . . . . 226
Controlling Logical and Physical Access                                  226
Logical Access                                                227
Physical Access                                               228
REVIEW                                                          228
51 QUESTIONS                                               228
51 ANSWERS                                                229
Objective 5.2 Manage identification and authentication of people,
devices, and services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Identification and Authentication                                       229
Identity Management Implementation                              230
Single/Multifactor Authentication                                 230
Accountability                                                 231
Session Management                                           232
Registration, Proofing, and Establishment of Identity                  232
Federated Identity Management                                  233
Credential Management Systems                                 233
Single Sign-On                                                234
Just-in-Time                                                  234
REVIEW                                                          235
52 QUESTIONS                                               236
52 ANSWERS                                                236
Objective 5.3 Federated identity with a third-party service . . . . . . . . 237
Third-Party Identity Services                                           237
On-Premise                                                   237
Cloud                                                        238
Hybrid                                                       238
REVIEW                                                          238
53 QUESTIONS                                               239
53 ANSWERS                                                239
Contents xix
Objective 5.4 Implement and manage authorization mechanisms. . . 239
Authorization Mechanisms and Models                                  240
Discretionary Access Control                                     241
Mandatory Access Control                                       241
Role-Based Access Control                                      242
Rule-Based Access Control                                      242
Attribute-Based Access Control                                   243
Risk-Based Access Control                                       243
REVIEW                                                          243
54 QUESTIONS                                               244
54 ANSWERS                                                244
Objective 5.5 Manage the identity and access provisioning
lifecycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Identity and Access Provisioning Life Cycle                               245
Provisioning and Deprovisioning                                  245
Role Definition                                                247
Privilege Escalation                                            248
Account Access Review                                              249
REVIEW                                                          251
55 QUESTIONS                                               251
55 ANSWERS                                                252
Objective 5.6 Implement authentication systems . . . . . . . . . . . . . . . . 252
Authentication Systems                                              252
Open Authorization                                             253
OpenID Connect                                               253
Security Assertion Markup Language                              253
Kerberos                                                     254
Remote Access Authentication and Authorization                    256
REVIEW                                                          257
56 QUESTIONS                                               257
56 ANSWERS                                                258
6.0 Security Assessment and esting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Objective 6.1 Design and validate assessment,
test, and audit strategies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
Defining Assessments, Tests, and Audits                                 260
Designing and Validating Evaluations                                    261
Goals and Strategies                                           261
Use of Internal, External, and Third-Party Assessors                   262
REVIEW                                                          263
61 QUESTIONS                                               263
61 ANSWERS                                                264
xx CISSP Passport

Objective 6.2 Conduct security control testing . . . . . . . . . . . . . . . . . . 264


Security Control Testing                                              264
Vulnerability Assessment                                        265
Penetration Testing                                             265
Log Reviews                                                  267
Synthetic Transactions                                          268
Code Review and Testing                                        268
Misuse Case Testing                                           269
Test Coverage Analysis                                         269
Interface Testing                                               269
Breach Attack Simulations                                       270
Compliance Checks                                             270
REVIEW                                                          271
62 QUESTIONS                                               271
62 ANSWERS                                                272
Objective 6.3 Collect security process data (e.g., technical and
administrative) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
Security Data                                                       272
Security Process Data                                           273
REVIEW                                                          275
63 QUESTIONS                                               276
63 ANSWERS                                                276
Objective 6.4 Analyze test output and generate report . . . . . . . . . . . . 277
Test Results and Reporting                                            277
Analyzing the Test Results                                       277
Reporting                                                    278
Remediation, Exception Handling, and Ethical Disclosure              278
REVIEW                                                          280
64 QUESTIONS                                               280
64 ANSWERS                                                280
Objective 6.5 Conduct or facilitate security audits . . . . . . . . . . . . . . . 281
Conducting Security Audits                                            281
Internal Security Auditors                                        282
External Security Auditors                                       282
Third-Party Security Auditors                                     283
REVIEW                                                          284
65 QUESTIONS                                               284
65 ANSWERS                                                284
Contents xxi

7.0 Security Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285


Objective 7.1 Understand and comply with investigations . . . . . . . . 286
Investigations                                                     
286
Forensic Investigations                                          287
Evidence Collection and Handling                                 287
Digital Forensics Tools, Tactics, and Procedures                      290
Investigative Techniques                                        291
Reporting and Documentation                                    292
REVIEW                                                         
293
71 QUESTIONS                                               294
71 ANSWERS                                                294
Objective 7.2 Conduct logging and monitoring activities. . . . . . . . . . 295
Logging and Monitoring                                              295
Continuous Monitoring                                          296
Intrusion Detection and Prevention                                296
Security Information and Event Management                        297
Egress Monitoring                                             297
Log Management                                              298
Threat Intelligence                                             298
User and Entity Behavior Analytics                                301
REVIEW                                                         
302
72 QUESTIONS                                               303
72 ANSWERS                                                304
Objective 7.3 Perform Configuration Management (CM)
(e.g., provisioning, baselining, automation) . . . . . . . . . . . . . . . . . 304
Configuration Management Activities                                   304
Provisioning                                                  305
Baselining                                                    305
Automating the Configuration Management Process                  306
REVIEW                                                          306
73 QUESTIONS                                               307
73 ANSWERS                                                307
Objective 7.4 Apply foundational security operations concepts . . . . 308
Security Operations                                                  308
Need-to-Know/Least Privilege                                    308
Separation of Duties and Responsibilities                           309
Privileged Account Management                                  310
Job Rotation                                                  311
Service Level Agreements                                       312
REVIEW                                                          313
74 QUESTIONS                                               314
74 ANSWERS                                                314
xxii CISSP Passport

Objective 7.5 Apply resource protection . . . . . . . . . . . . . . . . . . . . . . . 314


Media Management and Protection                                     315
Media Management                                            315
Media Protection Techniques                                     315
REVIEW                                                          317
75 QUESTIONS                                               317
75 ANSWERS                                                318
Objective 7.6 Conduct incident management . . . . . . . . . . . . . . . . . . . 318
Security Incident Management                                         318
Incident Management Life Cycle                                  319
REVIEW                                                          324
76 QUESTIONS                                               325
76 ANSWERS                                                326
Objective 7.7 Operate and maintain detective and preventative
measures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
Detective and Preventive Controls                                      326
Allow-Listing and Deny-Listing                                   327
Firewalls                                                     328
Intrusion Detection Systems and Intrusion Prevention Systems          331
Third-Party Provided Security Services                             332
Honeypots and Honeynets                                       333
Anti-malware                                                 334
Sandboxing                                                   335
Machine Learning and Artificial Intelligence                         336
REVIEW                                                          336
77 QUESTIONS                                               338
77 ANSWERS                                                338
Objective 7.8 Implement and support patch and vulnerability
management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
Patch and Vulnerability Management                                    339
Managing Vulnerabilities                                        339
Managing Patches and Updates                                  340
REVIEW                                                          342
78 QUESTIONS                                               342
78 ANSWERS                                                343
Objective 7.9 Understand and participate in change management
processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
Change Management                                                344
Change Management Processes                                  344
REVIEW                                                          347
79 QUESTIONS                                               347
79 ANSWERS                                                348
Contents xxiii
Objective 7.10 Implement recovery strategies . . . . . . . . . . . . . . . . . . . 348
Recovery Strategies                                                 348
Backup Storage Strategies                                       348
Recovery Site Strategies                                        351
Multiple Processing Sites                                        352
Resiliency                                                    355
High Availability                                               355
Quality of Service                                              356
Fault Tolerance                                                356
REVIEW                                                          357
710 QUESTIONS                                              358
710 ANSWERS                                               359
Objective 7.11 Implement Disaster Recovery (DR) processes. . . . . . . 359
Disaster Recovery                                                   359
Saving Lives and Preventing Harm to People                         360
The Disaster Recovery Plan                                            360
Response                                                    361
Personnel                                                    361
Communications                                               361
Assessment                                                  363
Restoration                                                   363
Training and Awareness                                         364
Lessons Learned                                               364
REVIEW                                                          365
711 QUESTIONS                                              366
711 ANSWERS                                               367
Objective 7.12 Test Disaster Recovery Plans (DRP). . . . . . . . . . . . . . . . 367
Testing the Disaster Recovery Plan                                      367
Read-Through/Tabletop                                         368
Walk-Through                                                 369
Simulation                                                    369
Parallel Testing                                                370
Full Interruption                                               370
REVIEW                                                          371
712 QUESTIONS                                              371
712 ANSWERS                                               372
Objective 7.13 Participate in Business Continuity (BC) planning
and exercises . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
Business Continuity                                                  372
Business Continuity Planning                                     373
Business Continuity Exercises                                    375
xxiv CISSP Passport

REVIEW                                                          376
713 QUESTIONS                                              376
713 ANSWERS                                               377
Objective 7.14 Implement and manage physical security . . . . . . . . . . 377
Physical Security                                                    377
Perimeter Security Controls                                      378
Internal Security Controls                                        382
REVIEW                                                          386
714 QUESTIONS                                              387
714 ANSWERS                                               387
Objective 7.15 Address personnel safety and security concerns . . . . 388
Personnel Safety and Security                                         388
Travel                                                       388
Security Training and Awareness                                  389
Emergency Management                                        389
Duress                                                       390
REVIEW                                                          391
715 QUESTIONS                                              391
715 ANSWERS                                               392
8.0 Sotware Development Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
Objective 8.1 Understand and integrate security in the Software
Development Life Cycle (SDLC) . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
Software Development Life Cycle                                       394
Development Methodologies                                     395
Maturity Models                                               398
Operation and Maintenance                                      400
Change Management                                           401
Integrated Product Team                                        401
REVIEW                                                          401
81 QUESTIONS                                               402
81 ANSWERS                                                403
Objective 8.2 Identify and apply security controls in software
development ecosystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
Security Controls in Software Development                               403
Programming Languages                                        404
Libraries                                                     405
Tool Sets                                                     406
Integrated Development Environment                              406
Runtime                                                      406
Continuous Integration and Continuous Delivery                      407
Security Orchestration, Automation, and Response                   407
Software Configuration Management                              408
Contents xxv
Code Repositories                                              408
Application Security Testing                                      408
REVIEW                                                          411
82 QUESTIONS                                               411
82 ANSWERS                                                412
Objective 8.3 Assess the effectiveness of software security. . . . . . . . 412
Software Security Effectiveness                                        412
Auditing and Logging Changes                                    413
Risk Analysis and Mitigation                                     413
REVIEW                                                          415
83 QUESTIONS                                               415
83 ANSWERS                                                415
Objective 8.4 Assess security impact of acquired software . . . . . . . . 416
Security Impact of Acquired Software                                   416
Commercial-off-the-Shelf Software                                416
Open-Source Software                                          417
Third-Party Software                                           417
Managed Services                                             418
REVIEW                                                          419
84 QUESTIONS                                               419
84 ANSWERS                                                420
Objective 8.5 Define and apply secure coding guidelines
and standards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
Secure Coding Guidelines and Standards                                 420
Security Weaknesses and Vulnerabilities at the Source-Code Level      420
Security of Application Programming Interfaces                      421
Secure Coding Practices                                         422
Software-Defined Security                                       424
REVIEW                                                          424
85 QUESTIONS                                               425
85 ANSWERS                                                425
A About the Online Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
System Requirements                                                427
Your Total Seminars Training Hub Account                                427
Privacy Notice                                                 427
Single User License Terms and Conditions                                427
TotalTester Online                                                   429
Technical Support                                                   429

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
This page intentionally left blank
DOMAIN xxvii

Acknowledgments

A book isn’t simply written by one person; so many people had key roles in the production o
this study guide, so I’d like to take this opportunity to acknowledge and thank them. First and
oremost, I would like to thank the olks at McGraw Hill, Wendy Rinaldi, Caitlin Cromley-
Linn, and Janet Walden. All three worked hard to keep me on track and made sure that this
book met the highest standards o quality. hey are awesome people to work with, and I’m
grateul once again to work with them!
I would also like to sincerely thank Nitesh Sharma, Senior Project Manager, Knowledge-
Works Global Ltd, who worked on the post-production or the book, and Bill McManus, who
did the copyediting work or the book. hey are also great olks to work with. Nitesh was so
patient and proessional with me at various times when I did not exactly meet a deadline and
I’m so grateul or that. I’ve worked with Bill a ew times on dierent book projects, and I must
admit I’m always in awe o him (and a bit intimidated by him, but really glad in the end to
have him help on my projects), since he is an awesome copyeditor who catches every single
one o the plentiul mistakes I make during the writing process. I have also gained a signiicant
respect or Bill’s knowledge o cybersecurity, as he’s always been able to key in on small nuances
o wonky explanations that even I didn’t catch and suggest better ways to write them. He’s the
perect person to make sure this book lows well, is understandable to a reader, and is a higher-
quality resource. hank you, Bill!
here are many other people on the production side who contributed signiicantly to the
publication o this book, including Rachel Fogelberg, ed Laux, homas Somers, and Je
Weeks, as well as others. My sincere thanks to them all or their hard work.
I also want to thank my amily or their patience and understanding as I took time away
rom them to write this book. I owe them a great deal o time I can never pay back, and I am
very grateul or their love and support.

xxvii
xxviii CISSP Passport

And last, but certainly not least, I want to thank the technical editor, Nichole O’Brien.
I’ve worked with Nichole on tons o real-world cybersecurity projects o and on or at least
ten years now. I’ve lost count o how many proposals, risk assessment reports, customer meet-
ings, and cyber-related problems she has suered through with me, yet she didn’t hesitate
to jump in and become the technical editor or this book. Nichole is absolutely one o the
smartest businesspeople I know in cybersecurity, as well as simply a really good person, and
I have an ininite amount o proessional and personal respect or her. his book is so much
better or having her there to correct my mistakes, ask critical questions, make me do more
research, and add a dierent and unique perspective to the process. hanks, Nichole!

—Bobby Rogers
DOMAIN xxix

Introduction

Welcome to CISSP Passport! his book is ocused on helping you to pass the Certiied Inor-
mation Systems Security Proessional (CISSP) certiication examination rom the Interna-
tional Inormation System Security Certiication Consortium, or (ISC)². he idea behind
the Passport series is to give you a concise study guide or learning the key elements o the
certiication exam rom the perspective o the required objectives published by (ISC)², in their
CISSP Certiication Exam Outline. Cybersecurity proessionals can review the experience
requirements set orth by (ISC)² at https://www.isc2.org/Certiications/CISSP/experience-
requirements. he basic requirement is ive years o cumulative paid work experience in two
or more o the eight CISSP domains, or our years o such experience plus either a our-year
college degree or an additional credential rom the (ISC)² approved list. (ISC)² requires that
you document this experience beore you can be ully certiied as a CISSP. For those candidates
who do not yet meet the experience requirements, they may achieve Associate o (ISC)² status
by passing the examination. Associates o (ISC)² are then allowed up to six years to accumulate
the required ive years o experience to become ull CISSPs.
he eight domains and the approximate percentage o exam questions they represent are
as ollows:

• Security and Risk Management (15%)


• Asset Security (10%)
• Security Architecture and Engineering (13%)
• Communication and Network Security (13%)
• Identity and Access Management (IAM) (13%)
• Security Assessment and esting (12%)
• Security Operations (13%)
• Sotware Development Security (11%)

CISSP Passport assumes that you have already studied long and hard or the CISSP exam
and now just need a quick reresher beore you take the exam. his book is meant to be a
“no lu ” concise study guide with quick acts, deinitions, memory aids, charts, and brie
explanations. Because this guide gives you the key concepts and acts, and not the in-depth

xxix
xxx CISSP Passport

explanations surrounding those acts, you should not use this guide as your only study source
to prepare or the CISSP exam. here are numerous books you can use or your deep studying,
such as CISSP All-in-One Exam Guide, Ninth Edition, also rom McGraw Hill.
I recommend that you use this guide to reinorce your knowledge o key terms and con-
cepts and to review the broad scope o topics quickly in the inal ew days beore your CISSP
exam, ater you’ve done all o your “deep” studying. his guide will help you memorize ast
acts, as well as reresh your memory about topics you may not have studied or a while.
his guide is organized around the most recent CISSP exam domains and objectives
released by (ISC)², which is May 1, 2021 at the time o writing this book. Keep in mind that
(ISC)² reserves the right to change or update the exam objectives anytime at its sole discretion
and without any prior notice, so you should check the (ISC)² website or any recent changes
beore you begin reading this guide and again a week or so beore taking the exam to make sure
you are studying the most updated materials.
he structure o this study guide parallels the structure o the eight CISSP domains pub-
lished by (ISC)², presented in the same numerical order in the book, with individual domain
objectives also ordered by objective number in each domain. Each domain in this guide is
equivalent to a regular book chapter, so this guide has eight considerably large “chapters” with
individual sections devoted to the objective numbers. his organization is intended to help
you learn and master each objective in a logical way. Because some domain objectives overlap,
you will see a bit o redundancy in topics discussed throughout the book; where this is the case,
the topic is presented in its proper context within the current domain objective and you’ll see
a cross-reerence to the other objective(s) in which the same topic is discussed.
Each domain contains the ollowing useul items to call out points o interest.

EXAM TIP Indicates critical topics you’re likely to see on the actual exam

NOTE Points out ancillary but pertinent information, as well as areas for
further study

CAUTION Warns you of common pitfalls, misconceptions, and potentially


harmful or risky situations when working with the technology in the real world
Introduction xxxi

Cross-Reference
Directs you to other places in the book where concepts are covered, for your reference

ADDITIONAL RESOURCES Identifies where you can find books, websites,


and other media for further assistance

he end o each objective gives you two handy tools. he “Review” section provides a
synopsis o the objective—a great way to quickly review the critical inormation. hen the
“Questions” and “Answers” sections enable you to test your newly acquired knowledge. For
urther study, this book includes access to online practice exams that will help to prepare you
or taking the exam itsel. All the inormation you need or accessing the exam questions is
provided in the appendix. I recommend that you take the practice exams to identiy where
you have knowledge gaps and then go back and review the relevant material as needed.
I hope this book is helpul to you not only in studying or the CISSP exam but also as a quick
reerence guide you’ll use in your proessional lie. hanks or picking this book to help you
study, and good luck on the exam!
This page intentionally left blank
M A
O I

N
Security and 1.0
Risk Management

Domain Objectives

• 1.1 Understand, adhere to, and promote professional ethics.


• 1.2 Understand and apply security concepts.
• 1.3 Evaluate and apply security governance principles.
• 1.4 Determine compliance and other requirements.
• 1.5 Understand legal and regulatory issues that pertain to information security
in a holistic context.
• 1.6 Understand requirements for investigation types (i.e., administrative,
criminal, civil, regulatory, industry standards).
• 1.7 Develop, document, and implement security policy, standards, procedures,
and guidelines.
• 1.8 Identify, analyze, and prioritize Business Continuity (BC) requirements.
• 1.9 Contribute to and enforce personnel security policies and procedures.
• 1.10 Understand and apply risk management concepts.
• 1.11 Understand and apply threat modeling concepts and methodologies.
• 1.12 Apply Supply Chain Risk Management (SCRM) concepts.
• 1.13 Establish and maintain a security awareness, education, and training
program.

1
2 CISSP Passport

Domain 1, “Security and Risk Management,” is one of the key domains in understanding
critical security principles that you will encounter on the CISSP exam. The majority of the
topics in this domain include the administrative or managerial security measures put in
place to manage a security program. In this domain you will learn about professional ethics
and important fundamental security concepts. We will discuss governance and compliance,
investigations, security policies, and other critical management concepts. We will also
delve into business continuity, personnel security, and the all-important risk management
processes. We’ll also discuss threat modeling, explore supply chain risk management, and
finish the domain by examining the different aspects of security training and awareness
programs. These are all very important concepts that will help you to understand the subse-
quent domains, since they provide the foundations of knowledge you need to be successful
on the exam.

Objective 1.1 Understand, adhere to, and promote


professional ethics

T he fact that (ISC)2 places professional ethics as the first objective in the first domain of
the CISSP exam requirements speaks volumes about the importance of ethics and ethi-
cal behavior in our profession. The continuing increases in network breaches, data loss, and
ransomware demonstrate the criticality of ethical conduct in this expanding information secu-
rity landscape. Our information systems security workforce is expanding at a rapid pace, and
these new recruits need to understand the professional discipline required to succeed. Some
may enter the field because they expect to make a lot of money, but ultimately competence,
integrity, and trustworthiness are the qualities necessary for success. Most professions have
published standards for ethical behavior, such as healthcare, law enforcement, accounting, and
many other professions. In fact, you would be hard-pressed to find a profession that does not
have at least some type of minimal ethical requirements for professional conduct.
While exam objective 1.1 is the only objective that explicitly covers ethics and professional
conduct, it’s important to emphasize them, since you will be expected to know them on the
exam and, more importantly, you will be expected to uphold them to maintain your CISSP sta-
tus. The first part of this exam objective covers the core ethical requirements from (ISC)2 itself.
Absent any other ethical standards that you may also be required to uphold in your profession,
from your organization, your customers, and even any other certifications you hold, the (ISC)2
Code of Ethics should be sufficient to guide you in ethical behavior and professional conduct
while you are employed as an information systems security professional for as long as you hold
the CISSP certification. The second part of the objective reviews other sources of professional
ethics that guide your conduct, such as those from industry or professional organizations.
First, let’s look at the (ISC)2 Code of Ethics.
DOMAIN 1.0 Objective 1.1 3

The (ISC)2 Code of Ethics


The (ISC)2 Code of Ethics, located on the (ISC)2 website at https://www.isc2.org/Ethics#,
consists of a preamble and four mandatory canons. Additionally, the web page includes a
comprehensive set of ethics complaint procedures for filing ethics complaints against certified
members. The complaint procedures are designed to detail how someone might formally
accuse a certified member of violating one or more of the four canons.

NOTE (ISC)2 updates the Code of Ethics from time to time, so it is best to
occasionally go to the (ISC)2 website and review it for any changes. This allows you
to keep up with current requirements and serves to remind you of your ethical and
professional responsibilities.

Code of Ethics Preamble


The Code of Ethics Preamble simply states that people who are bound to the code must adhere
to the highest ethical standards of behavior, and that the code is a condition of certification.
Per the (ISC)2 site (https://www.isc2.org/Ethics#), the preamble states (at the time of writing):

“The safety and welfare of society and the common good, duty to our principals, and to
each other, requires that we adhere, and be seen to adhere, to the highest ethical stand-
ards of behavior. Therefore, strict adherence to this Code is a condition of certification.”

Code of Ethics Canons


The Code of Ethics Canons dictate the more specific requirements that certification holders
must obey. According to the ethics complaint procedures detailed by (ISC)2, violation of any of
these canons is grounds for the certificate holder have their certification revoked. The canons
are as follows:

I. Protect society, the common good, necessary public trust and confidence, and the
infrastructure.
II. Act honorably, honestly, justly, responsibly, and legally.
III. Provide diligent and competent service to principals.
IV. Advance and protect the profession.

Obviously, these canons are intentionally broad and, unfortunately, someone could con-
strue them to fit almost any type of act by a CISSP, accidental or malicious, into one these
categories. However, the ethics complaint procedures specify a burden of proof involved with
making a complaint against the certification holder for violation of these canons. The com-
plaint procedures, set forth in the “Standing of Complainant” section, specify that “complaints
4 CISSP Passport

will be accepted only from those who claim to be injured by the alleged behavior.” Anyone
with knowledge of a breach of Canons I or II may file a complaint against someone, but only
principals, which are employers or customers of the certificate holder, can lodge a complaint
about any violation of Canon III, and only other certified professionals may register com-
plaints about violations of Canon IV.
Also according to the ethics complaint procedures, the complaint goes before an ethics
committee, which hears complaints of breaches of the Code of Ethics Canons, and makes a
recommendation to the board. But the board ultimately makes decisions regarding the validity
of complaints, as well as levees the final disciplinary action against the member, if warranted.
A person who has had an ethics complaint lodged against them under these four canons has a
right to respond and comment on the allegations, as there are sound due process procedures
built into this process.

EXAM TIP You should be familiar with the preamble and the four canons of
the (ISC)2 Code of Ethics for the exam. It’s a good idea to go to the (ISC)2 website and
review the most current Code of Ethics shortly before you take the exam.

Organizational Code of Ethics


The second part of exam objective 1.1 encompasses organizational standards and codes of
ethics. Most organizations today have some minimal form of a code of ethics, professional
standards, or behavioral requirements that you must obey to be a member of that organization.
“Organization” in this context means professional organizations, your workplace, your cus-
tomer organization, or any other formal, organized body to which you belong or are employed
by. Whether you are a government employee or a private contractor, whether you work for a
volunteer agency or work in a commercial setting, you’re likely required to adhere to some type
of organizational code of ethics. Let’s examine some of the core requirements most organiza-
tional codes of ethics have in common.

Workplace Ethics Statements and Policies


Codes of ethics in the workplace may or may not be documented. Often there is no formalized,
explicit code of ethics document published by the organization, although that may not be the
case, especially in large or publicly traded corporations. More often than not, the requirements
for ethical or professional behavior are stated as a policy or group of policies that apply not
only to the security professionals in the organization but to every employee. For example, there
are usually policies that cover the topics of acceptable use of organizational IT assets, personal
behavior toward others, sexual harassment and bullying, bribery, gifts from external parties,
and so on. Combined, these policies cover the wide range of professional behavior expecta-
tions. These policies may be sponsored and monitored by the human resources department
and are likely found in the organization’s employee handbook. For the organizations that have
DOMAIN 1.0 Objective 1.1 5
explicit professional ethics documents, these usually describe general statements that are not
specific to IT or cybersecurity professionals and direct the employee to behave ethically and
professionally in all matters.

Other Sources for Ethics Requirements


Although not directly testable by the CISSP exam, it’s worth noting that there are other sources
for ethics requirements for technology professionals in general and cybersecurity professionals
in particular. All of these sources contain similar requirements to act in a professional, hon-
est manner while protecting the interests of customers, employers, and other stakeholders, as
well as maintain professional integrity and work toward the good of society. The following
subsections describe several sources of professional ethics standards to give you an idea of how
important ethics and professional behavior are across the wide spectrum of not only cyberse-
curity but technology in general.

The Computer Ethics Institute


The Computer Ethics Institute (CEI) is a nonprofit policy, education, and research group
founded to promote the study of technology ethics. Its membership includes several tech-
nology-related organizations and prominent technologists and it is positioned as a forum for
public discussion on a variety of topics affecting the integration of technology and society. The
most well-known of its efforts is the development of the Ten Commandments of Computer
Ethics, which has been used as the basis of several professional codes of ethics and behavior
documents, among them the (ISC)2 Code of Ethics.
The Ten Commandments of Computer Ethics, presented here from the CEI website, are
as follows:

1. Thou shalt not use a computer to harm other people.


2. Thou shalt not interfere with other people’s computer work.
3. Thou shalt not snoop around in other people’s computer files.
4. Thou shalt not use a computer to steal.
5. Thou shalt not use a computer to bear false witness.
6. Thou shalt not copy or use proprietary software for which you have not paid.
7. Thou shalt not use other people’s computer resources without authorization or proper
compensation.
8. Thou shalt not appropriate other people’s intellectual output.
9. Thou shalt think about the social consequences of the program you are writing or the
system you are designing.
10. Thou shalt always use a computer in ways that ensure consideration and respect for
your fellow humans.
6 CISSP Passport

Institute of Electrical and Electronics


Engineers – Computer Society
The Institute of Electrical and Electronics Engineers (IEEE) published a professional Code of
Ethics designed to promulgate ethical behaviors among technology professionals. Although
the IEEE Code of Ethics does not specifically target cybersecurity professionals, its principles
similarly promote the professional and ethical behaviors of other technology professionals and
is similar in requirements to the (ISC)2 Code of Ethics. The more important points of the IEEE
Code of Ethics are summarized as follows:

• Uphold high standards of integrity, responsible behavior, and ethical conduct in


professional activities
• Hold paramount the safety, health, and welfare of the public
• Avoid real or perceived conflicts of interest
• Avoid unlawful conduct
• Treat all persons fairly and with respect
• Ensure the code is upheld by colleagues and coworkers

As you can see, these points are directly aligned with the (ISC)2 Code of Ethics and, as with
many codes of conduct, offer no conflict with other codes that members may be subject to. In
fact, since codes of ethics and professional behavior are often similar, they support and serve
to strengthen the requirements levied on various individuals.

ADDITIONAL RESOURCES In addition to the example of the IEEE Code of


Ethics, numerous other professional organizations that are closely related to or aligned
with cybersecurity professionals also have comparable codes that are worth mentioning.
Another noteworthy example is the Project Management Institute (PMI) Code of Ethics
and Professional Conduct, available at https://www.pmi.org/about/ethics/code.

Governance Ethics Requirements


There also are standards that are imposed as part of regulatory requirements that cover how
technology professionals will comport themselves. Some of these standards don’t specifically
target cybersecurity professionals per se, but they do prescribe ethical behaviors with regard
to data protection, for example, and apply to organizations and personnel alike. Almost all
data protection regulations, such as the EU’s General Data Protection Regulation (GDPR), the
U.S. Health Insurance Portability and Accountability Act (HIPAA), the National Institute of
Standards and Technology (NIST) publications, the Code of Ethics requirements spelled out
in Section 406 of the Sarbanes-Oxley Act of 2002, and countless other laws and regulations,
describe the actions that users and personnel with privileged access to sensitive data must take
to protect that data from a legal and ethical perspective in order to comply with security, pri-
vacy, and other governance requirements.
DOMAIN 1.0 Objective 1.1 7

REVIEW
Objective 1.1: Understand, adhere to, and promote professional ethics In this objective
we focused on one of the more important objectives for the CISSP exam—one that’s often
overlooked in exam prep. We discussed codes of ethics, which are requirements intended
to guide our professional behavior. We specifically examined the (ISC)2 Code of Ethics,
as that is the most relevant to the exam. The Code of Ethics consists of a preamble and
four mandatory canons. (ISC)2 also has a comprehensive set of complaint procedures for
ethics complaints against certified members. The complaint procedures detail the process
for formally accusing a certified member of violating one or more of the four canons, while
ensuring a fair and impartial due process for the accused.
We also examined organizational ethics and discussed how some organizations may not
have a formalized code of ethics document, but their ethical or professional behavior expec-
tations may be contained in their policies. These are usually found in policies such as accept-
able use, acceptance of gifts, bribery, and other types of policies. Most of the policies that
affect professional behavior for employees are typically found in the employee handbook.
Finally, we discussed other sources of professional ethics, from professional organi-
zations and governance requirements that may define how to protect certain sensitive
data classifications. Absent any other core ethics document that prescribes professional
behavior, the (ISC)2 Code of Ethics is mandatory for CISSP certification holders and
should be used to guide their behavior.

1.1 QUESTIONS
1. You’re a CISSP who works for a small business. Your workplace has no formalized
code of professional ethics. Your manager recently asked you to fudge the results of
a vulnerability assessment on a group of production servers to make it appear as if
the security posture is improving. Absent a workplace code of ethics, which of the
following should guide your behavior regarding this request?
A. Your own professional conscience
B. (ISC)2 Code of Ethics
C. Workplace Acceptable Use Policy
D. The Computer Ethics Institute policies
2. Nichole is a security operations center (SOC) supervisor who has observed one of her
CISSP-certified subordinates in repeated violation of both the company’s requirements
for professional behavior and the (ISC)2 Code of Ethics. Which of the following
actions should she take?
A. Report the violation to the company’s HR department only
B. Report the violation to (ISC)2 and the HR department
C. Ignore a one-time violation and counsel the individual
D. Report the violation to (ISC)2 only
8 CISSP Passport

3. Which of the following is a legal, ethical, or professional requirement levied upon an


individual to protect data based upon the specific industry, data type, and sensitivity?
A. (ISC)2 Code of Ethics
B. IEEE Code of Ethics
C. The Sarbanes-Oxley Code of Ethics requirements
D. The Computer Ethics Institute’s Ten Commandments of Computer Ethics
4. Bobby has been accused of violating one of the four canons of the (ISC)2 Code of Ethics.
A fellow cybersecurity professional has made the complaint that Bobby intentionally
wrote a cybersecurity audit report to reflect favorably on a company in which he is also
applying for a job in order to gain favor with its managers. Which of the following four
canons has Bobby likely violated?
A. Provide diligent and competent service to principals
B. Act honorably, honestly, justly, responsibly, and legally
C. Advance and protect the profession
D. Protect society, the common good, necessary public trust and confidence, and
the infrastructure

1.1 ANSWERS
1. B Absent any other binding code of professional ethics from the workplace, the
(ISC)2 Code of Ethics binds certified professionals to a higher standard of behavior.
While using your own professional judgment is admirable, not everyone’s professional
standards are at the same level. Workplace policies do not always cover professional
conduct by cybersecurity personnel specifically. The Computer Ethics Institute policies
are not binding to cybersecurity professionals.
2. B Since the employee has violated both the company’s professional behavior
requirements and the (ISC)2 Code of Ethics, Nichole should report the actions to
both entities. Had the violation been only that of the (ISC)2 Code of Ethics, she would
not have necessarily needed to report it to the company. One-time violations may be
accidental and should be handled at the supervisor’s discretion; however, repeated
violations may warrant further action depending upon the nature of the violation
and the situation.
3. C The Sarbanes-Oxley (SOX) Code of Ethics requirements are part of the regulation
(Section 406 of the Act) enacted to prevent securities and financial fraud and require
organizations to enact codes of ethics to protect financial and personal data. The
other choices are not focused on data sensitivity or regulations, but rather apply to
technology and cybersecurity professionals.
4. A Although the argument can be made that falsifying an audit report could violate any
or all of the four (ISC)2 Code of Ethics Canons, the scenario specifically affects the canon
that requires professionals to perform diligent and competent service to principals.
DOMAIN 1.0 Objective 1.2 9

Objective 1.2 Understand and apply security concepts

I n this objective we will examine some of the more fundamental concepts of security.
Although fundamental, they are critical in understanding everything that follows, since
everything we will discuss in future objectives throughout all CISSP domains relates to the
goals of security and their supporting tenets.

Security Concepts
To become certified as a CISSP, you must have knowledge and experience that covers a
wide variety of topics. However, regardless of the experience you may have in the different
domains, such as networking, digital forensics, compliance, or penetration testing, you need
to comprehend some fundamental concepts that are the basis of all the other security knowl-
edge you will need in your career. This core knowledge includes the goals of security and its
supporting principles.
In this objective we’re going to discuss this core knowledge, which serves as a reminder for
the experience you likely already have before attempting the exam. We’ll cover the goals of
security as well as the supporting tenets, such as identification, authentication, authorization,
and nonrepudiation. We will also discuss key supporting concepts such as principles of least
privilege and separation of duties. You’ll find that no matter what expertise you have in the
CISSP domains, these core principles are the basis for all of them. As we discuss each of these
core subjects we’ll talk about how different topics within the CISSP domains articulate to these
areas. First, it’s useful to establish common ground with some terms you’ll likely see through-
out this book and your studies for the exam.

Data, Information, Systems, and Entities


There are terms that we commonly use in cybersecurity that can cause confusion if every-
one in the field does not have a mutual understanding of what the terms mean. Our field is
rich with acronyms, such as MAC, DAC, RBAC, IdM, and many more. Often the same acro-
nym can stand for different terms. For example, in information technology and cybersecurity
parlance, MAC can stand for media access control, message authentication code, mandatory
access control, and memory access controller, not to mention that it’s also a slang term for a
Macintosh computer. That’s an example of why it’s important to define a few terms up front
before we get into our discussion of security concepts. These terms include data, information,
system, and entity (and its related terms subject and object).
Two terms often used interchangeably by technology people in everyday conversation are
data and information. In nontechnical discussion, the difference really doesn’t matter, but
as cybersecurity professionals, we need to be more precise in our speech and differentiate
10 CISSP Passport

between the two. For purposes of this book, and studying for the exam, data are raw, singular
pieces of fact or knowledge that have no immediate context or meaning. An example might be
an IP address, or domain name, or even an audit log entry, which by itself may not have any
meaning. Information is data organized into context and given meaning. An example might be
several pieces of data that are correlated to show an event that occurred on host at a specific
time by a specific individual.

EXAM TIP The CISSP exam objectives do not distinguish the differences
between the terms “information” and “data,” as they are often used interchangeably
in the profession as well. For the purposes of this book, we also will sometimes not
distinguish the difference and use the term interchangeably, depending on the context
and the exam objectives presented.

A system consists of multiple components such as hardware, software, network protocols,


and even processes. A system could also consist of multiple smaller systems, sometimes called
a system of systems but most frequently just referred to as a system, regardless of the type or
quantity of subsystems.
An entity, for our purposes, is a general, abstract term that includes any combination of
organizations, persons, hardware, software, processes, and so on, that may interact with peo-
ple, systems, information, or data. Frequently we talk about users accessing data, but in real-
ity, software programs, hardware, and processes can also independently access data and other
resources on a network, regardless of user action. So it’s probably more correct to say that an
entity or entities access these resources. We can assign accounts and permissions to almost
any type of entity, not just humans. It’s also worth noting that entities are also referred to as
subjects, which perform actions (read, write, create, delete, etc.) on objects, which are resources
such as computers, systems, and information.
Now that we have those terms defined, let’s discuss the three goals of security—confidentiality,
integrity, and availability.

Confidentiality
Of the three primary goals of information security, confidentiality is likely the one that most
people associate with cybersecurity. Certainly, it’s important to make sure that systems and data
are kept confidential and only accessed by entities that have a valid reason, but the other goals
of security, which we will discuss shortly, are also of equal importance. Confidentiality is about
keeping information secret and, in some cases, private. It requires protecting information that
is not generally accessible to everyone, but rather only to a select few. Whether it’s personal
privacy or health data, proprietary company information, classified government data, or just
simply data of a sensitive nature, confidential information is meant to be kept secret. In later
objectives we will discuss different access controls, such as file permissions, encryption, authen-
tication schemes, and other measures, that are designed to keep data and systems confidential.
DOMAIN 1.0 Objective 1.2 11
Integrity
Integrity is the goal of security to ensure that data and systems are not modified or destroyed
without authorization. To maintain integrity, data should be altered only by an entity that has
the appropriate access and a valid reason to modify. Obviously, data may be altered purpose-
fully for malicious reasons, but accidental or unintentional changes may be caused by a well-
intentioned user or even by a bad network connection that degrades the integrity of a file or
data transmission. Integrity is assured through several means, including identification and
authentication mechanisms (discussed shortly), cryptographic methods (e.g., file hashing),
and checksums.

Availability
Availability means having information and the systems that process it readily accessible by
authorized users any time and in any manner they require. Systems and information do users
little good if they can’t get to and use those resources when needed, and simply preventing
their authorized use contradicts the availability goal. Availability can be denied accidentally
by a network or device outage, or intentionally by a malicious entity that destroys systems and
data or prevents use via denial-of-service attacks. Availability can be ensured through various
means including equipment redundancy, data backups, access control, and so on.

Supporting Tenets of Information Security


Security tenets are processes that support the three goals of security. The security tenets are
identification, authentication, authorization, auditing, accountability, and nonrepudiation.
Note that these may be listed differently or include other principles, depending on the source
of knowledge or the organization.

Identification
Identification is the act of presenting credentials that state (assert) the identity of an individ-
ual or entity. A credential is a piece of information (physical or electronic) that confirms the
identity of the credential holder and is issued by an authoritative source. Examples of creden-
tials used to identify an entity include a driver’s license, passport, username and password
combination, smart card, and so forth.

Authentication
Authentication occurs after identification and is the process of verifying that the credential
presented matches the actual identity of the entity presenting it. Authentication typically
occurs when an entity presents an identification and credential, and the system or network
verifies that credential against a database of known identities and characteristics. If the iden-
tity and credential asserted matches an entry in the database, the entity is authenticated.
12 CISSP Passport

Once this occurs, an entity is considered authenticated to the system, but that does not mean
that they have the ability to perform any actions with any resources. This is where the next
step, authorization, comes in.

Authenticity
Authenticity goes hand-in-hand with authentication, in that it is the validation of a user, an
action, a document, or other entity through verified means. User authenticity is established
with strong authentication mechanisms, for example; an action’s authenticity is established
through auditing and accountability mechanisms, and a document’s authenticity might be
established through integrity checks such as hashing.

Authorization
Authorization occurs only after an entity has been authenticated. Authorization determines
what actions the entity can take with a given resource, such as a computer, application, or
network. Note that it is possible for an entity to be authenticated but have no authorization
to take any action with a resource. Authorization is typically determined by considering an
individual’s job position, clearance level, and need-to-know status for a particular resource.
Authorization can be granted by a system administrator, a resource owner, or another entity
in authority. Authorization is often implemented in the form of permissions, rights, and privi-
leges used to interact with resources, such as systems and information.

EXAM TIP Remember that authorization consists of the actions an individual can
perform, and is based on their job duties, security clearance, and need-to-know,

Auditing and Accountability


Accountability is the ability to trace and hold an entity responsible for any actions that entity
has taken with a resource. Accountability is typically achieved through auditing. Auditing is
the process of reviewing all interactions between an entity and an object to evaluate the effec-
tiveness of security controls. An example is auditing access to a network folder and being able
to conclusively determine that user Gary deleted a particular document in that folder. Audit-
ing would rule out that another user performed this action on that resource. Most resources,
such as computers, data, and information, can be audited for a variety of actions, such as
access, creation, deletion, and so forth. The most frequent manifestation of auditing is through
audit trails or logs, which are generated by the system or object being audited and record all
actions that any user takes with that system or object.

Nonrepudiation
To hold entities, such as users, accountable for the actions they perform on objects, we must
be able to conclusively connect their identity to an event. Auditing is useful for recording
Another random document with
no related content on Scribd:
CHAPTER XXXV
THE PHOTOGRAPH

B enton King sat in his office at the mill, opening the morning mail,
which had just been brought him by a boy. His face wore a
heavy frown, and he ripped open the envelopes viciously with the
steel paper cutter.
The sounds of the mill—the creaking of the windlass drawing the
big sticks up the run, the scream of the saws tearing through logs,
the pistol-claps of fresh-cut boards tossed flatly upon other boards
by the laborers—annoyed him, and he rose and kicked shut the
connecting door, which had been left slightly ajar.
Resuming his seat at the desk, his eye fell on a square, flat
package at the bottom of the letters remaining unopened, and he
caught it up eagerly.
“Ha!” he breathed, after looking at the address. “Fletcher’s
handwriting! He got it! This is what I sent for.”
Even as he was tearing off the wrapper, however, hesitation and
fear came upon him. What if it should not be what he wanted? What
if the photograph he knew the wrapping contained were not that of
the man he had accused? The possibility gave him a gripping throb
that was keen as the thrust of steel.
“It must be,” he muttered huskily. “I can’t be wrong. He has put up
a big bluff, but he’s the man.”
His hands were not wholly steady as he finished removing the
wrapper of brown manila. The picture was faced with cardboard, and
this he flung aside, revealing the printed likeness that had been
caught by the camera. Snatching it up, he turned eagerly to permit
the light to fall full upon it. His face flamed with triumph; his mouth
opened, but no sound issued forth; his clenched fist rose and fell on
the desk as if the blow settled the doom of a mortal foe. After a time
he laughed; it was not a pleasant laugh.
Presently, when he had gazed until satisfied that even the most
obtuse or most obstinate could not behold it and express a doubt as
to the almost perfect likeness of the picture to the man who called
himself Tom Locke, a likeness far stronger than a mere
verisimilitude, he turned again swiftly to the letters that had not yet
been opened. Running them over, he selected one on which the
writing corresponded to that upon the wrapper that had been
removed from the photograph. No time was wasted in opening it.

New York, June 28, 19—.


Dear Bent: Found an opportunity yesterday to run
out to Princeton and get the photograph of Paul
Hazelton, which you desire so urgently, and I am
sending it under separate cover, letter rates, so it will
travel along without delay. Why didn’t you tell me more
fully what you want of the thing? Night letters by wire
are cheap, and even a brief explanation would not
have left me puzzling my brains in weather that will
hatch eggs without the assistance of either setting hen
or incubator. You’re lucky to be up there in the open
pastures on the border of the big woods, where you
can breathe without fancying you are stoking an
Atlantic liner.
Crisply,
Fletch.

“Good old Fletch!” chuckled Bent. “I’ll write him about it later. He
has done me a great service, and Janet, also. This settles the matter
beyond any question or dispute.”
He looked at his watch; it was nine-thirty. Late enough for him to
see Janet, he decided, and, thrusting the letter and the photograph
into his pocket, he rose from the desk, leaving the remainder of the
mail unopened.
The screams of the mill saws followed him into the streets of the
town, and at times it seemed as if their cries of conquering triumph
took on something resembling entreaty or warning, but his hurrying
feet did not falter, and soon he was ringing at the parsonage door.
The white-capped maid answered and said she would find out if Miss
Harting could see him. He entered and waited.
He did not have to wait long before Janet appeared, his
heartstrings giving a tug as he beheld her in a simple morning gown.
In her blue eyes there was a look of wonder, not wholly free from
apprehension.
“I—I could hardly believe you were here—so early,” she said,
scanning his face as if seeking to find there some explanation of this
unusual call. “Has—has anything happened?”
“I beg your pardon for coming at this hour,” he returned, “but I
simply couldn’t wait. I hope you understand me and believe me,
Janet, when I say that I am your sincere friend, something I hope to
prove to your entire satisfaction. Taking the privilege of a friend
whose motives cannot be questioned, I must tell you how much I
regret having seen you yesterday with the man who calls himself
Locke.”
Her face did not harden, for there was nothing of hardness in her
nature, but it changed, warning him that he was treading on most
dangerous ground. She lifted her hand quickly, retreating a step.
“If that is what brings you here, I am sorry you came. I met Mr.
Locke quite by accident while out walking with the children. Jimmy
Bryant cut his foot frightfully on a broken bottle, and Mr. Locke bound
it up and brought him in to the doctor. I hardly know why I should
make this explanation.”
“You could not be seen with the man without arousing more or less
comment, and you should know what the gossips of this town will
say.”
“Mr. Locke has satisfied me that he is a thorough gentleman, and
unwarranted gossip of narrow-minded persons who are eager for
something to talk about cannot frighten me.” The color was in her
cheeks now.
“A gentleman!” cried Bent, losing his head for a moment. “That
two-faced sneak a gentleman! That man who has boasted already
that, as you happen to be the prettiest girl in town, he proposes to
amuse himself with you! He thinks himself a crusher, the sort that
girls get stuck on. He has the post-card photograph of one now, who
signs herself ‘Tid,’ doubtless a silly creature he has flattered and
fooled with his lying tongue. And now he proposes to get you on the
string and—”
“Stop, Benton King!” Her cheeks had lost the flush, and there was
something in her voice he had never heard before. “Whatever your
motive, you are making a blunder. How do you know these things
you are saying?”
CHAPTER XXXVI
CRUMBLED CASTLES

F earing what she might think of him for dealing with a man like
Hutchinson, he dared not tell her just how the knowledge had
come to him; but he swore it was true, that he knew it was true, and
begged her to believe him.
“And, though he has denied it, he is Paul Hazelton. They have the
absolute proof, and Mike Riley holds a letter of his that will bar him
from baseball in the Northern League. There’ll be a meeting called
this very week, and he’ll be suspended.”
“I do not believe it, I told you not to speak to me again about him
until you could show proof that—”
“I can! I have it here!”
Exultantly he produced the letter and photograph; the latter he
held before her eyes, and she looked at it, speechless.
“The picture of Paul Hazelton, of Princeton,” he said. “Does it
resemble Mr. Tom Locke?”
“Where—where did you get it?” she asked in a husky whisper,
taking it from his hand with nerveless fingers that nearly let it fall.
“I told you I had sent to a friend, asking him to get Hazelton’s
picture for me. He went to Princeton for it; here’s the name of the
Princeton photographer on it.”
She had hoped that there might be some doubt; that, even though
the photograph resembled Locke, there might be some question as
to whether it was not the counterfeit presentment of a person who
looked like him. But, with it before her eyes, that hope sank and died;
it was the man.
Watching her face, King felt certain he had won at last. He took the
picture, and placed the open letter in her hands. She tried to read it,
but the lines ran into a blurred mass, and finally, with a choking
sensation in her throat, she handed it back, endeavoring to keep him
from seeing how hard she was hit.
He sought to crush back and control his exultation; did his best to
prevent any touch of it from creeping into his voice.
“While I am sorry, Janet, that you were deceived, even for a
minute, by the fellow, I am also glad that no real harm has been
done. He has been exposed in time. I knew from the first that he lied
brazenly when he denied that he was Hazelton, but he certainly can
assume a plausible manner which might fool almost anybody. Henry
Cope knew, all along, that he was not what he represented himself to
be, but, on account of Riley’s claim, and to protect Hazelton, he
would not tell the truth. It is useless for him to hold back any longer. I
hope you do not blame me, Janet; I’m sure you won’t when you have
time to think it all over calmly. I care for you more—much more—
than I have ever let you know, and for that reason I—”
“Please don’t say anything more to me now,” she entreated, her
voice low but steady. “You were right.”
Half turning away, she put out her hand; he seized it quickly, and
found it cold.
“I’ll not say anything more now,” he breathed, close to her
shoulder, holding the hand fast in his grasp; “but some time, Janet—
some time when you are ready to listen—I’ll have something more to
say.”
On the street he swung off with a free, vigorous stride, his heart
beating high. He had won; he was sure of it. The knowledge of her
interest in the man, which he had feared might develop into
something deeper, had led him to realize the full extent of his own
regard for her. She was a poor clergyman’s daughter, and he was
the son of Cyrus King, but the little god had winged his arrow
straight, and the wound was deliciously deep.
Twenty minutes after King left, Janet, having donned hat and
wrap, came out and walked swiftly down the street. Her face was
chill and sad; she was deserted by hope; yet she would see Henry
Cope.
Behind his counter, the grocer peered at her over his glasses.
“Mornin’, Janet,” he said cheerfully. “’Nother ruther nice day.”
“Mr. Cope, I’d like to speak with you a moment privately.”
Surprised, he took note of her pallor and the girl’s troubled look.
Her voice had an unusual sound. Pushing up his spectacles, he
came from behind the counter.
“Step inter my office,” he invited.
In the office he urged her to sit down, saying she looked tired; but
she preferred to stand.
“I’ll bother you only a minute,” she said.
“No bother at all—no bother. What can I do? Anything the matter?”
“I have come to ask you, confidentially, about—about the man who
is called Tom Locke.” She half turned her head away.
“Eh? Oh, him? What you want t’ know?”
“Mr. Cope, I want you to tell me the truth. You need not fear that I
will repeat anything you say. You have always been my friend, and
now, as such, I ask you to answer my question. I hope you’ll not
refuse or put me off.”
“You bet I’ve alwus been your friend, little girl,” he returned
earnestly. “What’s the question?”
“You engaged Mr. Locke for the baseball team, and you know who
he is. They are saying he is a Princeton College man by the name of
Hazelton. Tell me, Mr. Cope, if that is true.”
“Now, what makes the difference who he is?” spluttered the
grocer, frowning. “I’m bein’ pestered to death about him.”
“I’m sorry; I didn’t mean to pester you. I gave you my word I would
not repeat anything you told me, but if you will not answer my
question—”
“Hold on, Janet; I ain’t said I wouldn’t answer it. I know you won’t
tell if you say ye won’t, and, anyhow, it’s beginnin’ to look like he’d
have to sail under his own colors before long. Yes, Miss Janet, he’s
Paul Hazelton. I agreed t’ keep mum ’bout it so’s he wouldn’t git inter
a mess ’bout pitchin’ for his college; but what’s the use, with Mike
Riley raisin’ high jinks an’ claimin’ he’s got a holt on the boy, and
even settin’ the newspapers to buzzin’? I’m ruther sorry for Hazelton,
but I s’pose he knew he was takin’ a chance when he come here.”
“That’s all,” said the girl; “thank you. Now, I hope you’ll not tell
anybody that I came to you to inquire about him?”
“Not a peep, little girl. He’s a mighty nice feller, I’ll say that fer him.
Don’t seem to have no bad habits, an’ goes t’ church, an’—”
But she did not wait to hear him enumerate the virtues of the man
who had looked straight into her eyes and lied without a tremor; the
man who was proud of his conquests with the fair sex, and had
boasted that he would amuse himself with her while in Kingsbridge.
What a despicable creature the fellow was! She left the store.
On the way back home, Janet passed several persons without
noticing them at all, but she kept her face set with the fixed purpose
of preventing any one who saw her from imagining that she was
fighting back a flood of tears. Glad that her father was out for a
morning walk, she avoided the maid, hurried to her room, locked the
door, and permitted the flood to burst the restraining gates.
After a time, having “cried it out,” she sat in an easy-chair near the
window, watching a mother robin on her nest in the tree outside.
She was not thinking of the robin, however; she was thinking of
yesterday and the meeting in the woods—a day she had thought the
happiest of her life. She was thinking of the manner in which Locke
had looked at her with those clear, honest brown eyes, and how she
had thrilled beneath that look. She was thinking of his voice as,
sitting on the log and leaning toward her, he had quoted the words of
Bassanio, causing the heart, now cold and heavy in her breast, to
leap and throb until it seemed that he must hear its joyous beating.
No man had ever stirred her like that, and something told her that
no other man could so stir her again. And all the time he had been
playing with her—amusing himself!
That day, “the happiest of her life,” was a day to regret; a day to
forget—if she could forget it. Would the sun ever again shine as
brightly? Would the woods ever seem so shadowy cool and inviting?
Would the flowers ever be so fair and sweet?
She had loved the world and everything in it, and her blood had
danced in her veins, and her feet had longed to dance, despite it
being the Sabbath day; her very soul had seemed to sing with a joy
as wide as eternity.
Now the sun was shining outside her window, but there was
something gone from its golden glamour; her blood that had danced
flowed chill in her body, and her heart was full with a pain too great
for it to contain.
“A dream,” she whispered dully—“nothing but a dream. It is over!”
CHAPTER XXXVII
THE BELL BOY

O n Wednesday Bancroft was to play again in Kingsbridge, and


Thursday was to be the “middle of the week lay-off” for both the
Bullies and the Kinks.
Tuesday’s early mail brought Henry Cope a letter bearing the
Bancroft postmark, and he opened it somewhat nervously. As he
apprehended, it contained a communication from Anson Graham,
president of the Northern League, giving notice that there would be
held at the office of Rufus Kilgore, in Bancroft, on Thursday evening,
at eight o’clock, a meeting of the league directors to consider the
protest of Manager Riley relative to Paul Hazelton, “playing with
Kingsbridge under the assumed name of Tom Locke.”
“By gum!” growled the grocer disgustedly. “They actually do mean
business. We’re up ag’inst it. The boy better know ’bout this right
away.”
He found Locke making ready to start for Fryeburg, where the
team was to play that afternoon. The young man seemed strangely
depressed, and his face wore a deep frown as he read the notice,
which Cope had handed him. The grocer anxiously regarded the
expression on the pitcher’s face.
“Well?” he asked, as Tom returned the notice.
“It is fortunate,” said Locke grimly, “that I fancied this meeting
might be called on short notice, and made preparations for it.”
“Hey? You’ve made preparations?”
“Yes.”
“Whut sort o’ preparations?”
“Don’t worry, Mr. Cope; I shall be ready for them, I think.”
“Then you’re dead sartin old Riley ain’t got no holt on ye?”
“How many times,” asked the young pitcher impatiently, “must I tell
you so, Mr. Cope?”
“You know it’s got round somehow that you’ve denied p’int-blank
that you’re Hazelton, and some folks—they’s alwus that kind in ev’ry
town—are sayin’ they reckon you lied,” stammered the grocer. “You
ain’t never denied that your name’s Hazelton, have ye?”
Tom Locke frowned, but made no answer to the question.
“As fur’s I’m concerned,” said Cope, “when they’ve tried to corner
me, I’ve dodged or refused to answer. It’s too bad, boy; I’m mighty
sorry it’s all goin’ to come out who ye be, but ’twarn’t my fault. I’ve
kep’ my part of our agreement.”
“I haven’t any doubt of that. It’s simply the result of unfortunate
circumstances and the determination of somebody to do me a bad
turn. Mr. Cope, I’m not a trouble breeder, but, as you have used me
square and I am genuinely interested in the team, I’m going to give
you a tip to keep an eye on your manager. Nor does this come
wholly, or even mainly, from the fact that I do not like him personally;
I have reasons to believe that he is not on the level.”
“Hum!” grunted the grocer; “we hired him on good
recommendation, but I don’t mind tellin’ you privately that I’ve got a
feelin’ myself that he ain’t to be trusted too fur. He’s fer puttin’ you on
the bench until arter this fuss over you is settled, an’ that don’t sound
good t’ me. I want you to pitch agin’ Bancroft ag’in to-morrer.”
“And I want to pitch against them,” said Tom warmly; “but you’ll
find that Hutchinson will object.”
“As long as you insist that they can’t count out the games that you
win, I’m goin’ to set on the bench myself an’ see that you pitch to-
morrer.”
“Good! I hope I’m in my best form, for I hear that Riley has had his
men batting industriously in practice against a left-handed pitcher.
Being left-handed helped me against his left-handed hitters at first
before I had them sized up; but I’ve made a study of them for weak
spots, and, though they are called sluggers, he has no Wagners or
Lajoies—men who can bump any kind of a ball that comes within
reach of their bats. They have their failings, every one of them, and,
with good control and good support, I should be able to take another
fall out of them.”
The door of the room had been left slightly ajar by Cope. Outside
that door a hesitating bell boy stood listening to the talk of the two
men. Hearing some one turn the knob of a door farther along the
corridor, the boy hastily lifted his hand and knocked. At Locke’s call,
he pushed the door open, and entered.
“Hello, Sam,” said the pitcher. “On the bed there—that suit needs
pressing; take it to the tailor, will you, and tell him I want it back to-
night? Here!”
He extended a silver half dollar, but the boy, who had gathered up
the suit of dark-blue serge from the bed, drew back, looking
confused.
“What’s the matter, Sam?” asked Locke, a bit impatiently. “You’ve
been doing some little favors for me of late.”
“I’d rather not take it, sir,” said the boy, his lids lowered and his
gaze on the floor. “I hope ye don’t mind, sir.”
“Why, I don’t understand—”
“You—you was good to my little brother, Jimmy, when he cut his
foot, and—and I’d rather not take anything, sir.”
Locke laughed for the first time that day, slipping the piece of silver
into the genuinely unwilling hand of the boy.
“I reckon I owe Jimmy and his friends something, instead of the
shoe being on the other foot,” he said enigmatically. “So Jimmy is
your brother? I didn’t know that. You haven’t a high opinion of me as
a pitcher, have you, Sam?”
“Oh, I was jest talkin’ to hear myself talk,” answered the boy
quickly, his face turning crimson. “Did Jimmy tell you that?”
“I overheard it quite by accident. How’s his foot?”
“Oh, he ain’t caperin’ round on it much yit; but it’ll be all right pretty
soon. I wisht you’d take this half back. Paw, he asked the doc, and
the doc, he said there warn’t nothin’ t’ pay for tendin’ Jimmy’s foot,
’cause you had paid; an’ I’d like ter do somethin’ to sorter make it
square.”
“All right; keep the half now, and we’ll begin afresh. Now that I
know I can do it, I’ll impose on you frightfully; I’ll keep you hopping
for me in great shape. Say, hustle along and get that suit to the tailor,
or he’ll not have it pressed for me to wear this evening; and I may
want it.” He swung the door wide open, pushed the boy out, and
closed it behind him.
“Fust time,” observed Henry Cope, “I ever knew a Bryant t’ try to
refuse money. They’re a pretty shif’less, worthless bunch, that
family.”
CHAPTER XXXVIII
“AND DID NOT UNDERSTAND”

A short time later, with his playing suit in the hand bag he carried,
Locke left the hotel and started for the railway station, where he
would join the other members of the team, all of whom, save
Hutchinson and himself, were stopping at a boarding house. As he
swung down the street, Janet Harting came out of a store and turned
toward him. He saw her, and his heart jumped. She saw him, and in
a moment she turned squarely around and hastened the other way,
vanishing beyond the first corner.
He knew she had seen him this time and deliberately avoided him;
there could be no question about it. The evening before he had
come upon her suddenly on the street, lifted his hat, and spoken; but
she had passed on without a word or a token to betray that he had
been observed.
Although it seemed impossible then that she had failed to see him,
he was not positive; now, however, he knew, and the knowledge left
him breathless and dazed. When he reached the corner beyond
which she had disappeared she was far along the street, and
hurrying as if in great fear that he would pursue her.
“It’s too much for me,” he murmured. “It’s got me guessing.
There’s no getting around it, she dodged me. Why? She saw me last
night, and did not speak. Why? I can hardly believe it of her. What
have I done? She is the last person I’d ever fancied would do
anything of the sort.”
He did not long remain in doubt, for he was not a dull-witted man.
The controversy about him was the cause of it all; she had heard
what every one in Kingsbridge who took the slightest interest in
baseball had heard, and she believed that he had spoken falsely to
her. Impulsive, indignant, scornful, she wished to have nothing
further to do with a man who could look straight into her eyes and tell
her an untruth without a blush or as much as the turning of a hair.
“That’s it,” he said. “There’s no other explanation. I must call on
her this evening, after we get back, and tell her the straight truth.”
The truth! If he had not been truthful, was he silly enough to fancy
penitence would help him now?
The day proved tiresome and wretched for Tom Locke, and it was
far from satisfactory for his teammates, with Fryeburg winning
through a ninth-inning rally that tied the score and a batting streak in
the tenth which earned them the run they needed, with only one out.
Stark, seeing the pitcher had wilted, and fearing the batters who
were coming up, asked Hutchinson to call Lefty in to save the day;
but the manager grimly refused.
The train bore the defeated players back to a late supper in
Kingsbridge, for up there supper was the evening meal. On the way,
Jack Hinkey asked if any one had heard anything about Bancroft’s
new pitcher, and the others confessed that they had not.
“Feller tole me t’-day,” said Hinkey, “that Riley had signed a new
twirler who’d be run in agin’ us t’-morrer. An’ he’s a port-side flinger
by the name of Craddock. Anybody ever hear of him?”
They confessed that they had not. Locke was the only man who
did not answer. Sitting some seats ahead of the others and on the
opposite side of the car, he was gazing glumly out at the whirling
landscape, his face as dark as the purple shadows hovering at the
base of a distant line of hills.
“Hey, Tom,” called Larry Stark, “did you get what Hink was telling
us?”
Locke started, shook himself a bit, and turned.
“I was thinking just then,” he said. “What was it?”
They told him, and he acknowledged that he knew of no pitcher by
the name of Craddock.
“They say he’s a hot article,” said Hinkey. “Feller that tole me ’bout
him seemed to think we was goin’ to git up ag’inst the real thing t’-
morrer.”
“What you tryin’ to do,” growled Sockamore, “frighten Lefty? Look
at him. He’s fergot about Craddock a’ready.”
Locke was again gazing out of the window in a preoccupied,
moody manner.
“Whut’s the matter with him?” wondered Hunchy Oulds. “He’s
been like that ’most all day. He must be in love—or sick.”
“Same t’ing,” grinned Labelle.
“Hope he don’t go gittin’ off his feed now,” muttered Hinkey. “He’s
due t’ git his bumps some time, but I’d like ter see him pull through t’-
morrer, ’specially if they do spring a new pitcher on us.”
“Maybe,” said Reddy Crandall, “Hutch won’t work him to-morrow. I
was told by a Fryeburger that there was a meetin’ comin’ on for
Thursday to settle whuther Lefty belongs to us or not, and maybe the
games he’s pitched won’t be counted.”
“They can’t throw them out!” snapped Stark savagely. “They’ve got
to count them. And if we lose Locke we’re going to be in bad.”
“You mean Hazelton, don’t ye?” grinned Hinkey. “They say it’s
settled that that’s his right name. As a rule, I don’t think much of
college guys, but I own up that Lefty is some pitcher, and we’ll miss
him.”
Despite his words, his tone was not suggestive of worriment.
Hinkey was one of the men brought to the team by Bob Hutchinson.
Tom Locke did not eat much that night. He hurried to the dining
room at the Central Hotel. Two cups of coffee, hot and strong, made
the greater part of his meal. They steadied him.
Dashing up to his room, he found the blue serge suit, freshly
pressed and carefully laid out on his bed. It took him twenty minutes
to make a complete change, even though he was possessed by an
almost feverish desire to hurry. And, as a rule, when he hurried he
could do it in half that time.
Taking a final peep at himself in the mirror, he extinguished the
light and went out. When bidding him adieu on Sunday, the girl had
invited him to call some time, and he proposed to do so this evening.
As he drew near the parsonage, however, he faltered, and his
pace slackened. She had shunned him upon the street; would she
not refuse to see him now?
“She must give me a chance to explain,” he muttered desperately.
“Surely she’ll do that. I can’t believe she’ll decline to see me for a few
minutes, at least.”
Locke’s pulse beat rapidly. With his handkerchief he wiped his
forehead. It was ridiculous, of course, for a man like him to flush and
shiver like a big boy suffering from his first attack of calf love; but, try
as he might, he could not steady himself as he approached the
cottage and discovered that, though the curtains were drawn, there
was a light in the parlor.
Perhaps Benton King was there! Well, what of it? Was he the man
to turn back and leave the field to a rival? Were King there, it was all
the more reason why he should make haste to put himself right in
her eyes. His jaws set, he followed the walk to the front door, and
rang.
One of the parlor windows, near by, was open, but the shade was
drawn well down, so that anybody within the room could not be seen
by a person outside who might seek to look in. As he turned in from
the street, he had fancied he caught the sound of voices drifting out
through that window, and one was, he believed, that of Janet.
Presently the maid came, and he asked for Miss Harting. “I haven’t
a card,” he said. “Please tell her it is Mr. Locke, who would like to
see her a few minutes.”
He was left standing in the hall, which was lighted by the soft glow
of a shaded lamp. In a brief time the maid returned.
“Miss Harting is engaged,” she said, “and cannot see you.”
It seemed that his heart stopped beating, and he stood quite still,
unwilling to believe it could be true. The maid opened the door. He
passed out with the step of a somnambulist.
So, after all, she was that sort of a girl! Only the thoughtless and
shallow render judgment without a proper hearing and an
investigation. He had thought her something more than a girl easily
swayed and swept away by every light, shifting wind; but it now
seemed that he had invested her with imaginary qualities and a
character which she did not possess.
The door closed behind him. His feet threatened to drag as he
walked toward the gate. Suddenly he stiffened at the sound of a
laugh heard through the open window. His teeth clicked, his hands
clenched, and every nerve in his body seemed to jerk taut as a
bowstring. King was there—laughing!
He had turned to face the window, and for a few seconds he stood
perfectly rigid and motionless. He struck no pose, made no gesture;
but he, too, laughed, silently.
“Last time we met,” he breathed at length, “you called me a liar,
Benton King, and I held myself. If you were to repeat that word to me
to-night, I’d knock you down in your tracks.”
His step was steady enough now as he walked away. For a
moment he thought of returning to the hotel and writing her a letter,
stating the truth briefly; but he dismissed the idea almost
immediately.
“She’ll find out in time,” he said; “for the whole of Kingsbridge will
know after the meeting Thursday night. When she does find out,
perhaps she’ll be sorry for her mistake, but it will be too late.”
CHAPTER XXXIX
BANCROFT COMES TO CONQUER

N ever before, even though it was the middle of the week, had
such a crowd of Bancroft fans accompanied the team to a
neighboring town. When the train stopped they began hopping off
the cars, like fleas from the back of a cat to which insect powder has
been applied, and in a few moments the station platform was packed
with them, laughing, joking, confident of what the afternoon held in
store.
In short order they swarmed into every restaurant in town. Having
satisfied their hunger, they went forth into the streets of Kingsbridge
to wait for the hour of the game, some of them to seek citizens who
were willing to back the local team with real money.
But Fancy Dyke and two associates, provided with rolls of the
“long green,” had struck Kingsbridge by an earlier train and raked the
place for bets with a fine-tooth comb. Kingsbridgers who had money
they were willing to risk sought the assurance of Henry Cope that
Tom Locke would pitch; and, with this guarantee, they proceeded to
“take a chance.”
Before the gates opened that afternoon, more money had been
posted than ever before on a single game in the Northern League.
For, while the milltown people had heard that the Bullies would
present a new left-handed slabman, the promise that Locke would
do the tossing for the Kinks left them still with a feeling of assurance
undisturbed by the least uncertainty.
Not that they believed there was no chance of losing, but their faith
in Lefty was so great that it seemed at least a five-to-one shot in
Kingsbridge’s favor; and a man who would “squeeze his roll” with
such an opportunity staring him in the face certainly lacked sporting
blood.
That afternoon, as the hour of the game drew on, only the
unyielding strictness of foremen and bosses kept the mills running,
the workmen almost threatening to desert in a body. Some of them
slipped away, even though they knew they were inviting discharge by
doing so.
Naturally, the curiosity to see Bancroft’s new pitcher was very
great, and there was a mighty craning of necks on the bleachers and
in the stand when the visitors appeared for practice.
The man whose name had been given as Craddock was easily
seen, being over six feet in height, and having amazingly long arms
and legs; in fact, he seemed to be nearly all arms and legs. He was
not a handsome person, with a hatchet face and a huge beak of a
nose, while his ears stood out like fans on either side of his long,
narrow head. He carried his shoulders hunched forward, and walked
with a queer bobbing movement of the knees, a sort of buckling with
each step. In more ways than one his appearance was suggestive of
a crane.
Craddock warmed up without letting himself loose at all, giving the
eager watchers no chance to get an idea of his capability by
anything in that preliminary performance.
With the appearance of the home team, Hutchinson sprang a
surprise. A new man came on the field with them, a bronzed, husky,
rawboned man, who quickly set the crowd to speculating as to his
identity. When the local pitchers began limbering their wings, one
question was quickly answered; for when the stranger commenced
to warm up, also, it was seen that he was a pitcher; and many a
Kingsbridger hoped he would prove to be better than either Deever
or Skillings.
Mike Riley, smoking industriously, stood around with his hands in
his pockets, watching his players in a self-satisfied manner. His
bearing was more than encouraging for those who had journeyed
thirty miles to see the Bullies win. After a time, he walked over and
spoke to Hutchinson. They talked earnestly for several minutes,
Riley making gestures with his clenched fist and nodding his head
savagely, while Hutch shrugged his shoulders repeatedly.

You might also like