My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
J.P. MORGAN CHASE BANK-2016
Clerk
>
Contracts / Agreements
>
J
>
J.P. MORGAN CHASE BANK-2016
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/31/2017 12:58:30 PM
Creation date
1/10/2017 3:43:03 PM
Metadata
Fields
Template:
Contracts
Company Name
JP MORGAN CHASE BANK
Contract #
A-2016-366
Agency
FINANCE & MANAGEMENT SERVICES
Council Approval Date
12/6/2016
Expiration Date
12/31/2019
Insurance Exp Date
6/1/2017
Destruction Year
0
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
341
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
J.P. Morgan's Response to Clarification Questions for the City of Santa Ana <br />RFP No. 16 -111 Banking Services <br />1. In terms of Internal Audit Controls, do you have Audit and Event Log reports available on your <br />system? If, so please provide a copy of a report sample and include in demonstration. <br />J.P. Morgan ACCESS does provide an Audit and Event Log under the Tools menu available from any <br />screen within the system. Our Audit and Control Logs allow you to perform searches based on <br />individual or a group of users by a specific date range with a variety of filters including product type <br />(Checks, Reports, Payments, etc.), detail type (Imported File, Report Type, etc.), and event /activity <br />type (File Format, Report Name, etc.). Results can be viewed online or downloaded PDF, Excel and <br />CSV format <br />This process will be reviewed during the demonstration; we have also attached a screenshot in the <br />appendix of this document for your reference. <br />2. Describe how your system safeguards against an individual user, including an administrator, from <br />being able to initiate and release an electronic payment. <br />J.P. Morgan ACCESS automatically prevents a single user from performing all actions (create, <br />approve and release) on a single payment, even if the user is entitled to create, approve and release. <br />For those functions that demand an extra level of security, ACCESS provides two - factor <br />authentication via RSA SecurlD® token technology. <br />The City can setup ACCESS with strict controls over user access to functions and accounts. This also <br />helps to enforce compliance with internal audit requirements while enhancing security. Some of the <br />available fraud prevention options include: <br />• Enabling IP filtering to restrict access by limiting authorized users' ability to log on from only IP <br />addresses you designate. <br />• Customizing the payment approval process by creating rules that determine the number and <br />identity of approvers for different types of transactions, including separate approval rules for <br />repetitive templates and free form wires, as well as the order in which that review must occur. <br />• Separating duties, accounts and approval workflows, the City can help reduce the risk of fraud <br />or compromised data. The City's security administrators are the only individuals able to assign <br />users with transaction initiation privileges. <br />• Limiting each ACCESS user to a single, designated computer. <br />• Establishing transaction and daily aggregate limits at the account and user level. <br />• Creating templates with payment details to prevent wires from being initiated and executed <br />without prior approval of the recipient bank account numbers and template details. <br />We will address the process of entitling users for electronic payments during the demonstration. <br />
The URL can be used to link to this page
Your browser does not support the video tag.