Objective
1: Determine the scope for the examination of the institution’s
e-banking activities consistent with the nature and complexity of
the institution’s operations. |
| |
| 1.
|
Review
the following documents to identify previously noted issues related
to the e-banking area that require follow-up: |
| |

|
Previous
regulatory examination reports |
| |

|
Supervisory
strategy |
| |

|
Follow-up
activities |
| |

|
Work
papers from previous examinations |
| |

|
Correspondence |
| |
|
| 2. |
Identify
the e-banking products and services the institution offers, supports,
or provides automatic links to (i.e., retail, wholesale, investment,
fiduciary, e-commerce support, etc.). |
| |
|
| 3. |
Assess
the complexity of these products and services considering volumes
(transaction and dollar), customer base, significance of fee income,
and technical sophistication. |
| |
|
| 4. |
Identify
third-party providers and the extent and nature of their processing
or support services. |
| |
|
| 5.
|
Discuss
with management or review MIS or other monitoring reports to determine
the institution’s recent experience and trends for the following: |
| |

|
Intrusions,
both attempted and successful; |
| |

|
Fraudulent
transactions reported by customers; |
| |

|
Customer
complaint volumes and average time to resolution; and |
| |

|
Frequency
and duration of service disruptions. |
| |
|
| 6. |
Review audit and consultant reports, management’s responses,
and problem tracking systems to identify potential issues for examination
follow-up. Possible sources include: |
| |
|
Internal
and external audit reports and Statement of Accounting Standards 70
(SAS 70) reviews for service providers, |
| |
|
Security
reviews/evaluations from internal risk review or external consultants
(includes vulnerability and penetration testing), and |
| |
|
Findings
from GLBA security and control tests and annual GLBA reports to the
board. |
| |
|
| 7.
|
Review
network schematic to identify the location of major e-banking components.
Document the location and the entity responsible for development,
operation, and support of each of the major system components. |
| |
|
| 8.
|
Review
the institution’s e-banking site(s) to gain a general understanding
of the scope of e-banking activities and the website’s organization,
structure, and operability. |
| |
|
| 9.
|
Discuss
with management recent and planned changes in: |
| |
|
The
types of products and services offered; |
| |
|
Marketing
or pricing strategies; |
| |
|
Network
structure; |
| |
|
Risk
management processes, including monitoring techniques; |
| |
|
Policies,
processes, personnel, or controls, including strategies for intrusion
responses or business continuity planning; |
| |
|
Service
providers or other technology vendors; and |
| |
|
The
scope of independent reviews or the individuals or entities conducting
them. |
| |
|
| 10. |
Based
on the findings from the previous steps, determine the scope of the
e-banking review. Discuss, as appropriate, with the examiner or office
responsible for supervisory oversight of the institution. |
| |
|
Select
from among the following examination objectives and procedures those
that are appropriate to the examination’s scope. When more
in-depth coverage of an area is warranted, examiners should select
procedures from other booklets of the IT Handbook as necessary
(e.g., “Information Security Booklet,” “Retail
Payments Systems Booklet,” etc.). For more complex e-banking
environments, examiners may need to integrate IT coverage with business
line-specific coverage. In those cases, examiners should consult
other subject matter experts and consider inclusion of the member
agency’s expanded procedures (e.g., compliance, retail lending,
fiduciary/asset management, etc.). |
| |
|
BOARD
AND MANAGEMENT OVERSIGHT |
| |
|
|
Objective
2: Determine the adequacy of board and management oversight of e-banking
activities with respect to strategy, planning, management reporting,
and audit. |
| |
|
| 1. |
Evaluate
the institution’s short- and long-term strategies for e-banking
products and services. In assessing the institution’s planning
processes, consider whether: |
| |
|
The
scope and type of e-banking services are consistent with the institution’s
overall mission, strategic goals, operating plans, and risk tolerance; |
| |
|
The
institution’s MIS is adequate to measure the success of e-banking
strategies based on clearly defined organizational goals and objectives; |
| |
|
Management’s understanding of industry standards is sufficient
to ensure compatibility with legacy systems; |
| |
|
Cost-benefit
analyses of e-banking activities consider the costs of start-up, operation,
administration, upgrades, customer support, marketing, risk management,
monitoring, independent testing, and vendor oversight (if applicable); |
| |
|
Management’s
evaluation of security risks, threats, and vulnerabilities is realistic
and consistent with institution’s risk profile; |
| |
|
Management’s
knowledge of federal and state laws and regulations as they pertain
to e-banking is adequate; and |
| |
|
A
process exists to periodically evaluate the institution’s e-banking
product mix and marketing successes and link those findings to its
planning process. |
| |
|
| 2. |
Determine
whether e-banking guidance and risk considerations have been incorporated
into the institution’s operating policies to an extent appropriate
for the size of the financial institution and the nature and scope
of its e-banking activities. Consider whether the institution’s
policies and practices: |
| |
|
Include
e-banking issues in the institution’s processes and responsibilities
for identifying, measuring, monitoring, and controlling risks; |
| |
|
Define
e-banking risk appetite in terms of types of product or service, customer
restrictions (local/domestic/foreign), or geographic lending territory; |
| |
|
Consider,
if appropriate, e-banking activities as a mission-critical activity
for business continuity planning; |
| |
|
Assign
day-to-day responsibilities for e-banking compliance issues including
marketing, disclosures, and BSA/OFAC issues; |
| |
|
Require
e-banking issues to be included in periodic reporting to the board
of directors on the technologies employed, risks assumed, and compensating
risk management practices; |
| |
|
Maintain
policies and procedures over e-commerce payments (i.e., bill payment
or cash management) consistent with the risk and controls associated
with the underlying payment systems (check processing, ACH, wire transfers,
etc.); |
| |
|
Establish
policies to address e-commerce support services (aggregation, certificate
authority, commercial website hosting/design, etc.); |
| |
|
Include
e-banking considerations in the institution’s written privacy
policy; and |
| |
|
Require
the board of directors to periodically review and approve updated
policies and procedures related to e-banking. |
| |
|
| 3. |
Assess
the level of oversight by the board and management in ensuring that
planning and monitoring are sufficiently robust to address heightened
risks inherent in e-banking products and services. Consider whether: |
| |
|
The
board reviews, approves, and monitors e-banking technology-related
projects that may have a significant impact on the financial institution’s
risk profile; |
| |
|
The
board ensures appropriate programs are in place to oversee security,
recovery, and third-party providers of critical e-banking products
and services; |
| |
|
Senior
management evaluates whether technologies and products are in line
with the financial institution’s strategic goals and meet market
needs; |
| |
|
Senior
management periodically evaluates e-banking performance relative to
original/revised project plans; |
| |
|
Senior
management has developed, as appropriate, exit strategies for high-risk
activities; and |
| |
|
Institution
personnel have the proper skill sets to evaluate, select, and implement
e-banking technology. |
| |
|
| 4. |
Evaluate
adequacy of key MIS reports to monitor risks in e-banking activities.
Consider monitoring of the following areas: |
| |
|
Systems
capacity and utilization; |
| |
|
Frequency
and duration of service interruptions; |
| |
|
Volume
and type of customer complaints, including time to successful resolution; |
| |
|
Transaction
volumes by type, number, dollar amount, behavior (e.g., bill payment
or cash management transaction need sufficient monitoring to identify
suspicious or unusual activity); |
| |
|
Exceptions
to security policies whether automated or procedural; |
| |
|
Unauthorized
penetrations of e-banking system or network, both actual and attempted; |
| |
|
Losses
due to fraud or processing/balancing errors; and |
| |
|
Credit
performance and profitability of accounts originated through e-banking
channels. |
| |
|
| 5. |
Determine
whether audit coverage of e-banking activities is appropriate for
the type of services offered and the level of risk assumed. Consider
the frequency of e-banking reviews, the adequacy of audit expertise
relative to the complexity of e-banking activities, the extent of
functions outsourced to third-party providers. The audit scope should
include: |
| |
|
Testing/verification
of security controls, authentication techniques, access levels, etc.; |
| |
|
Reviewing
security monitoring processes, including network risk analysis and
vulnerability assessments; |
| |
|
Verifying
operating controls, including balancing and separation of duties;
and |
| |
|
Validating
the accuracy of key MIS and risk management reports. |
| |
|
|
Objective
3: Determine the quality of the institution’s risk management
over outsourced technology services. |
| |
|
| 1. |
Assess
the adequacy of management’s due diligence activities prior
to vendor selection. Consider whether: |
| |
|
Strategic
and business plans are consistent with outsourcing activity, and |
| |
|
Vendor
information was gathered and analyzed prior to signing the contract,
and the analysis considered the following: |
| |
|
 |
Vendor
reputation; |
| |
|
 |
Financial
condition; |
| |
|
 |
Costs
for development, maintenance, and support; |
| |
|
 |
Internal
controls and recovery processes; and |
| |
|
 |
Ability
to provide required monitoring reports. |
| |
|
| 2. |
Determine
whether the institution has reviewed vendor contracts to ensure
that the responsibilities of each party are appropriately identified.
Consider the following provisions if applicable: |
| |
|
Description
of the work performed or service provided; |
| |
|
Basis
for costs, description of additional fees, and details on how prices
may change over the term of the contract; |
| |
|
Implementation
of an appropriate information security program; |
| |
|
Audit
rights and responsibilities; |
| |
|
Contingency
plans for service recovery; |
| |
|
Data
backup and protection provisions; |
| |
|
Responsibilities
for data security and confidentiality and language complying with
the GLBA 501(b) guidelines regarding security programs; |
| |
|
Hardware
and software upgrades; |
| |
|
Availability
of vendor’s financial information; |
| |
|
Training
and problem resolution; |
| |
|
Reasonable
penalty and cancellation provisions; |
| |
|
Prohibition
of contract assignment; |
| |
|
Limitations
over subcontracting (i.e., prohibition or notification prior to engaging
a subcontractor for data processing, software development, or ancillary
services supporting the contracted service to the institution); |
| |
|
Termination
rights without excessive fees, including the return of data in a machine-readable
format in a timely manner; |
| |
|
Financial
institution ownership of the data; |
| |
|
Covenants
dealing with the choice of law (United States or foreign nation);
and |
| |
|
Rights
of federal regulators to examine the services, including processing
and support conducted from a foreign nation. |
| |
|
| 3.
|
Assess
the adequacy of ongoing vendor oversight. Consider whether the institution’s
oversight efforts include: |
| |
|
Designation
of personnel accountable for monitoring activities and services; |
| |
|
Control
over remote vendor access (e.g., dial-in, dedicated line, Internet);
|
| |
|
Review
of service provider’s financial condition; |
| |
|
Periodic
reviews of business continuity plans, including compatibility with
those of the institution; |
| |
|
Review
of service provider audits (e.g., SAS 70 reports) and regulatory examination
reports; and |
| |
|
Review
and monitoring of performance reports for services provided. |
| |
|
| INFORMATION
SECURITY PROCESS |
| |
|
| Objective
4: Determine if the institution’s information security program
sufficiently addresses e-banking risks. |
| |
|
| 1.
|
Determine
whether the institution’s written security program for customer
information required by GLBA guidelines includes e-banking products
and services. |
| |
|
| 2.
|
Discuss
the institution’s e-banking environment with management as
applicable. Based on this discussion, evaluate whether the examination
scope should be expanded to include selected Tier II procedures
from the IT Handbook’s “Information Security Booklet.”
Consider discussing the following topics: |
| |
|
Current
knowledge of attackers and attack techniques; |
| |
|
Existence
of up-to-date equipment and software inventories; |
| |
|
Rapid
response capability for newly discovered vulnerabilities; |
| |
|
Network
access controls over external connections; |
| |
|
Hardening
of systems; |
| |
|
Malicious
code prevention; |
| |
|
Rapid
intrusion detection and response procedures; |
| |
|
Physical
security of computing devices; |
| |
|
User
enrollment, change, and termination procedures; |
| |
|
Authorized
use policy; |
| |
|
Personnel training; |
| |
|
Independent
testing; and |
| |
|
Service
provider oversight. |
| |
|
| 3.
|
Determine
whether the security program includes monitoring of systems and
transactions and whether exceptions are analyzed to identify and
correct noncompliance with security policies as appropriate. Consider
whether the institution adequately monitors the following:
|
| |
|
Systems
capacity and utilization; |
| |
|
The
frequency and duration of service interruptions; |
| |
|
The volume and type of customer complaints, including time to resolution; |
| |
|
Transaction
volumes by type, number, and dollar amount; |
| |
|
Security
exceptions; |
| |
|
Unauthorized
penetrations of e-banking system or network, both actual and attempted
(e.g., firewall and intrusion detection system logs); and |
| |
|
E-banking
losses due to fraud or errors. |
| |
|
| 4. |
Determine the adequacy of the institution’s authentication
methods and need for multi-factor authentication relative to the
sensitivity of systems or transactions. Consider the following processes: |
| |
|
Account
access |
| |
|
Intrabank
funds transfer |
| |
|
Account
maintenance |
| |
|
Electronic
bill payment |
| |
|
Corporate
cash management |
| |
|
Other
third-party payments or asset transfers |
| |
|
| 5. |
If the institution uses passwords for customer authentication, determine
whether password administration guidelines adequately address the
following: |
| |
|
Selection
of password length and composition considering ease of remembering,
vulnerability to compromise, sensitivity of system or information
protected, and use as single- or multi-factor authentication; |
| |
|
Restrictions
on the use of automatic log-on features; |
| |
|
User
lockout after a number of failed log-on attempts – industry
practice is generally no more than 3 to 5 incorrect attempts; |
| |
|
Password
expiration for sensitive internal or high-value systems; |
| |
|
Users’
ability to select and/or change their passwords; |
| |
|
Passwords
disabled after a prolonged period of inactivity; |
| |
|
Secure
process for password generation and distribution; |
| |
|
Termination
of customer connections after a specified interval of inactivity –
industry practice is generally not more than 10 to 20 minutes; |
| |
|
Procedures
for resetting passwords, including forced change at next log-on after
reset; |
| |
|
Review
of password exception reports; |
| |
|
Secure
access controls over password databases, including encryption of stored
passwords; |
| |
|
Password
guidance to customers and employees regarding prudent password selection
and the importance of protecting password confidentiality; and |
| |
|
Avoidance
of commonly available information (i.e., name, social security number)
as user IDs. |
| |
|
| 6. |
Evaluate access control associated with employee’s administrative
access to ensure: |
| |
|
Administrative
access is assigned only to unique, employee-specific IDs; |
| |
|
Account
creation, deletion, and maintenance activity is monitored; and |
| |
|
Access
to funds-transfer capabilities is under dual control and consistent
with controls over payment transmission channel (e.g., ACH, wire transfer,
Fedline). |
| |
|
| 7. |
Evaluate the appropriateness of incident response plans. Consider
whether the plans include: |
| |
|
A
response process that assures prompt notification of senior management
and the board as dictated by the probable severity of damage and potential
monetary loss related to adverse events; |
| |
|
Adequate
outreach strategies to inform the media and customers of the event
and any corrective measures; |
| |
|
Consideration
of legal liability issues as part of the response process, including
notifications of customers specifically or potentially affected; and |
| |
|
Information-sharing
procedures to bring security breaches to the attention of appropriate
management and external entities (e.g., regulatory agencies, Suspicious
Activity Reports, information-sharing groups, law enforcement, etc.). |
| |
|
| 8.
|
Assess
whether the information security program includes independent security
testing as appropriate for the type and complexity of e-banking
activity. Tests should include, as warranted: |
| |
|
Independent
audits |
| |
|
Vulnerability
assessments |
| |
|
Penetration
testing |
| |
|
| Objective
5: Determine if the institution has implemented appropriate administrative
controls to ensure the availability and integrity of processes supporting
e-banking services. |
| |
|
| 1.
|
Determine
whether employee authorization levels and access privileges are
commensurate with their assigned duties and reinforce segregation
of duties. |
| |
|
| 2. |
Determine whether controls for e-banking applications include:
|
| |
|
Appropriate
balancing and reconciling controls for e-banking activity; |
| |
|
Protection
of critical data or information from tampering during transmission
and from viewing by unauthorized parties (e.g., encryption); |
| |
|
Automated
validation techniques such as check digits or hash totals to detect
tampering with message content during transmission; |
| |
|
Independent
control totals for transactions exchanged between e-banking applications
and legacy systems; and |
| |
|
Ongoing
review for suspicious transactions such as large-dollar transactions,
high transaction volume, or unusual account activity |
| |
|
| 3. |
Determine whether audit trails for e-banking activities are sufficient
to identify the source of transactions. Consider whether audit trails
can identify the source of the following: |
| |
|
On-line
instructions to open, modify, or close a customer’s account; |
| |
|
Any
transaction with financial consequences; |
| |
|
Overrides
or approvals to exceed established limits; and |
| |
|
Any
activity granting, changing, or revoking systems access rights or
privileges (e.g., revoked after three unsuccessful attempts). |
| |
|
| 4. |
Evaluate the physical security over e-banking equipment, media,
and communication lines. |
| |
|
| 5. |
Determine
whether business continuity plans appropriately address the business
impact of e-banking products and services. Consider whether the
plans include the following: |
| |
|
Regular
review and update of e-banking contingency plans; |
| |
|
Specific
staff responsible for initiating and managing e-banking recovery plans; |
| |
|
Adequate
analysis and mitigation of any single points of failure for critical
networks; |
| |
|
Strategies
to recover hardware, software, communication links, and data files;
and |
| |
|
Regular
testing of back-up agreements with external vendors or critical suppliers. |
| |
|
| LEGAL
AND COMPLIANCE ISSUES |
| |
|
| Objective
6: Assess the institution’s understanding and management of
legal and compliance issues associated with e-banking activities. |
| |
|
| 1. |
Determine how the institution stays informed on legal and regulatory
developments associated with e-banking and thus ensures e-banking
activities comply with appropriate consumer compliance regulations.
Consider: |
| |
|
Existence
of a process for tracking current litigation and regulations that
could affect the institution’s e-banking activities; |
| |
|
Assignment
of personnel responsible for monitoring e-banking legislation and
the requirements of or changes to compliance regulations; and |
| |
|
Inclusion
of e-banking activity and website content in the institution’s
compliance management program. |
| |
|
| 2. |
Review the website content for inclusion of federal deposit insurance
logos if insured depository services are offered (12 CFR 328 or
12 CFR 740). |
| |
|
| 3. |
Review the website content for inclusion of the following information
which institutions should consider to avoid customer confusion and
communicate customer responsibilities:
|
| |
|
Disclosure
of corporate identity and location of head and branch offices for
financial institutions using a trade name; |
| |
|
Disclosure
of applicable regulatory information, such as the identity of the
institution’s primary regulator or information on how to contact
or file a complaint with the regulator; |
| |
|
Conspicuous
notices of the inapplicability of FDIC/NCUA insurance to, the potential
risks associated with, and the actual product provider of, the specific
investment and insurance products offered; |
| |
|
Security
policies and customer usage responsibilities (including security disclosures
and Internet banking agreements); |
| |
|
On-line
funds transfer agreements for bill payment or cash management users;
and |
| |
|
Disclosure
of privacy policy — financial institutions are encouraged, but
not required, to disclose their privacy policies on their websites
— to include: |
| |
|
 |
“Conspicuous”
disclosure of the privacy policy on the website in a manner that complies
with the privacy regulation and |
| |
|
 |
Information
on how to “opt out” of sharing (if the institution shares
information with third parties). |
| |
|
| 4. |
If the financial institution electronically delivers consumer disclosures
that are required to be provided in writing, assess the institution’s
compliance with the E-Sign Act. Review to determine whether:
|
| |
|
The
disclosures: |
| |
|
 |
Are
clear and conspicuous; |
| |
|
 |
Inform
the consumer of any right or option to receive the record in paper
or non-electronic form; |
| |
|
 |
Inform
the consumer of the right to withdraw consent, including any conditions,
consequences, or fees associated with such action; |
| |
|
 |
Inform
consumers of the hardware and software needed to access and retain
the disclosure for their records; and |
| |
|
 |
Indicate
whether the consent applies to only a particular transaction or to
identified categories of records. |
| |
|
The
procedures the consumer uses to affirmatively consent to electronic
delivery reasonably demonstrate the consumer’s ability to access/view
disclosures. |
| |
|
| 5. |
Determine whether e-banking support services are in place to facilitate
compliance efforts, including:
|
| |
|
Effective
customer support by the help desk, addressing: |
| |
|
 |
Complaint
levels and resolution statistics, |
| |
|
 |
Performance
relative to customer service level expectations, and |
| |
|
 |
Review
of complaints/problems for patterns or trends indicative of processing
deficiencies or security weaknesses. |
| |
|
Appropriate
processes for authenticating and maintaining electronic signatures
(E-Sign Act). |
| |
|
| 6. |
As applicable, determine whether the financial institution has considered
the applicability of various laws and regulations to its e-banking
activities: |
| |
|
Monitoring
of potential money-laundering activities associated with e-banking
required by the Bank Secrecy Act (31 CFR 103.18); |
| |
|
Filing
of Suspicious Activity Reports for unusual or unauthorized e-banking
activity or computer security intrusions requirements (regulation
cites vary by agency); |
| |
|
Screening
of on-line applications and activity for entities/countries prohibited
by the Office of Foreign Asset Control (31 CFR 500 et. seq.); and |
| |
|
Authenticating
new e-banking customers using identification techniques consistent
with the requirements of Bank Secrecy Act (31 CFR 103) and the USA
PATRIOT Act [12 CFR 21 (OCC), 12 CFR 208 and 211 (Board), 12 CFR
326 (FDIC), 12 CFR 563 (OTS), and 12 CFR 748 (NCUA)]. |
| |
|
| 7.
|
|