My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Item 26 - Agreement with Allied Network Solutions, Inc. for Adobe Software and Subscription
Clerk
>
Agenda Packets / Staff Reports
>
City Council (2004 - Present)
>
2025
>
01/21/2025
>
Item 26 - Agreement with Allied Network Solutions, Inc. for Adobe Software and Subscription
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/27/2025 5:03:20 PM
Creation date
1/21/2025 2:16:24 PM
Metadata
Fields
Template:
City Clerk
Doc Type
Agenda Packet
Agency
Information Technology
Item #
26
Date
1/21/2025
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.
/
762
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
SOLICITATION # CH16012 <br />records (User ID, date, time, type of event, successful/unsuccessful attempts or access secured <br />files and protect the contents of audit trails against unauthorized access, modification or deletion. <br />VirtueStream <br />Virtustream offers logging as a managed service to customers as optional solution. The types of <br />services and devices are specified by the customer and a monthly report is delivered to the <br />customer. <br />8.6.7 Offeror must describe whether it can restrict visibility of cloud hosted data and documents to specific <br />users or groups. <br />CA <br />APM <br />Users of the Portal are divided into two types: Internal users (for publishers of the API) <br />and External users (for developers). There are a number of pre -defined roles for both <br />Internal and External users that inherit functionality in a hierarchical manner. Portal <br />has RBAC built in that allows you to grant access to different functionality for different <br />users. For example, you can assign a user to role that only allows them access to <br />update content, or access apps but not create them. <br />MAA <br />CA utilizes IaaS vendor to host the service with strict access controls in place. CA <br />SaaS InfoSec team manages users and their associations with groups within LDAP <br />Directory and conducts periodic access reviews to conform to governance <br />requirements. <br />CA Agile <br />Our databases are shared but logically segregated. We ensure logical security of <br />access to customer data by implementing access restrictions between subscriptions <br />and roles within those subscriptions to assure adequate segregation of data. There is <br />a plugin available in the unlimited edition that allows the administrator to limit access <br />to the application based on IP address. <br />ASM <br />Only Public Status Page (PSP) data is stored in the cloud, and PSP web pages are <br />accessible by anyone. PSP data is only sent to the cloud if the customer enables this <br />feature, and they can decide which data is made public. <br />Google <br />If Google becomes aware of a Data Incident, Google will promptly notify Customer of the Data <br />Incident, and take reasonable steps to minimize harm and secure Customer Data. Notification(s) <br />of any Data Incident(s) will be delivered to the Notification Email Address provided by Customer in <br />connection with the Agreement or, at Google's discretion, by direct communication (e.g., by phone <br />call or an in -person meeting). Customer acknowledges that it is solely responsible for ensuring the <br />contact information given for purposes of the Notification Email Address is current and valid, and <br />for fulfilling any third party notification obligations. Customer agrees that "Data Incidents" do not <br />include: (i) unsuccessful access attempts or similar events that do not compromise the security or <br />privacy of Customer Data, including pings, port scans, denial of service attacks and other network <br />attacks on firewalls or networked systems; or (ii) accidental loss or disclosure of Customer Data <br />caused by Customer's use of the Services or Customer's loss of account authentication <br />credentials. Google's obligation to report or respond to a Data Incident under this Section will not <br />be construed as an acknowledgement by Google of any fault or liability with respect to the Data <br />Incident. <br />AODocs <br />The AODocs-specific data stored in the Google App Engine Datastore relies on a built-in multi - <br />tenancy feature named "namespace", which define virtual "silos" within the AODocs database. <br />Each customer is assigned a specific namespace (which is in fact the customer's primary Google <br />Apps domain name), and all the customer's data is stored within this namespace. <br />Virtru <br />Key material is encrypted prior to storage, and those keys are backed by HSM. Decryption occurs <br />only for authenticated users <br />Salesforce <br />The multitenant architecture and secure logical controls address separation of customer data. <br />There are no dedicated servers used for individual customers. The Salesforce Services <br />infrastructure is divided into a modular architecture based on "Instance". Each Instance is capable <br />carahsoft 76 carahsoft <br />
The URL can be used to link to this page
Your browser does not support the video tag.