My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
J.P. MORGAN CHASE BANK, N.A. 1A - 2015
Clerk
>
Contracts / Agreements
>
J
>
J.P. MORGAN CHASE BANK, N.A. 1A - 2015
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/13/2016 4:03:34 PM
Creation date
7/13/2016 3:57:09 PM
Metadata
Fields
Template:
Contracts
Company Name
J.P. MORGAN CHASE BANK, N.A.
Contract #
A-2015-303
Agency
FINANCE & MANAGEMENT SERVICES
Council Approval Date
12/15/2015
Expiration Date
12/31/2016
Insurance Exp Date
6/1/2017
Destruction Year
2021
Notes
a-2010-204
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
178
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
Proposal 'for 'the City of Santa Ana <br />.J.PM0r(;d11 <br />The City will have the ability to designate the rights of each user on the J.P. Morgan ACCESS <br />platform. Products on the portal are designed to accommodate a wide range of security options, <br />including requests for multiple transaction approvals, demands for separate "enter" and "release" <br />functions for users, dual control among users, along with daily or transaction limits. <br />The separation of duties and approval workflows provide mechanisms clients can use to help <br />ensure that no personnel can perform transactions to commit fraud or compromise the integrity of <br />the entitlement data. Client security administrators can assign these specific transaction initiation <br />privileges to users. <br />J.P. Morgan ACCESS security architecture provides authentication as well as authorization to <br />ensure that each User is permitted access to only the applications and functions established and <br />approved for their use. When highly sensitive (value- bearing or administrative) data is being <br />transmitted between the User and J.P. Morgan, additional security in the form of a digital <br />signature is required to ensure integrity. All communications between the User and J.P. Morgan <br />are secured using SSL protected sessions. <br />Basic Authentication / Single sign -an <br />In order to establish a session, the User must supply a valid User ID <br />and Password. This validation is managed by commercially available <br />single sign -on authentication software. Once a User sign -on is <br />complete, entitlements are verified for each User. The User's J.P.' -, <br />Morgan ACCESS screen displays only functions and accounts for - <br />which he or she has been entitled access. <br />RSA SecudDCP* <br />Only certain functions within J.P. Morgan ACCESS will require an additional level of security: <br />Security Administrator functions and Transaction initiation entitlements (Funds Transfer, ACH, <br />and Liquidity modules). In these cases, the User must use their SecurlD device to sign on and <br />release value hearing transactions. The SecurlD RSA token device is a small, hand -held device <br />that generates a six -digit security code every 60 seconds: This is referred to as a "token code ". <br />For these Users, the token code must be supplied with their ID and Password at sign on and <br />again at the point of transaction release. SecurlD technology provides a high level of security by <br />authenticating each user and digitally signing each transaction. All of this is done without the <br />need for locally installed software or hardware. Once a user has received their SecurlD device, <br />the start -up process is quick and easy. <br />'SecurlD is a registered trademark or trademark of RSA Security Inc. in the United States and/or <br />other countries. <br />Administration <br />The City's security administrators will maintain established authentication IDs and digital <br />signature authority. Additional users can be established and approved using the online <br />entitlement feature. <br />As a standard practice, J.P. Morgan requires two security administrators to be, involved in user <br />setup and maintenance to help clients maintain reasonable audit controls. Additionally, if security <br />administrators are to have product functions, two other security administrators must prepare and <br />approve the product function entitlements. Security administrators cannot request or approve <br />product functions (e.g., cash reporting, wire initiation, eta) for themselves unless an authorized <br />company representative has signed a special waiver. <br />One security administrator establishes users for accounts, services (ACH initiation, wire initiation, <br />balance reporting, etc.) and functions (transaction initiation, transaction approval, release, <br />reporting, etc.), while a different security administrator approves the users for the accounts, <br />services and functions established by the first security administrator. <br />Pane 20 <br />
The URL can be used to link to this page
Your browser does not support the video tag.