Technology_Security_Assessment_TSD-20271940.pdf
PDF 4 MB Posted
- Solicitation number
- TSD-20271940
- Issued by
- San Mateo County, California
About this file
This Technology Security Assessment document pertains to the County of San Mateo Technology Services Department's domain transition initiative. The County seeks to migrate all systems from the current smcgov.org domain to a .gov domain in compliance with California Assembly Bill 1637, which mandates that all local agencies adopt a .gov domain by January 1, 2029. The scope of work encompasses the technical migration of all County website domains and subdomains, email systems, Domain Name Systems (DNS), TSD-owned and managed enterprise applications integrated with Okta and Active Directory for authentication, enterprise platforms, and identification of departmental applications countywide that will be impacted by this domain transition. The assessment identifies critical technical dependencies, current infrastructure configurations, and system interdependencies necessary to support a comprehensive domain migration strategy.
The security assessment focuses on evaluating the current technological environment to ensure that the domain transition can be executed without compromising system security, data integrity, or operational continuity. The document provides technical baseline information regarding existing authentication systems, enterprise application architecture, and network infrastructure that will inform the subsequent implementation phase. This assessment is a prerequisite to the broader Domain Transition and Implementation Services RFP, establishing the technical foundation and risk mitigation strategies required for successful execution of the domain migration project before the January 1, 2029 statutory deadline.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Domain_Transition_and_Implementation_Services_RFP.pdf | ||
| Domain_Transition_and_Implementation_Services_RFP_TSD-20271940.pdf | ||
| References_Template_TSD-20271940.docx | DOCX document | |
| Standard_Contract_Template_TSD-20271940.docx | DOCX document | |
| Price_Proposal_Template_TSD-20271940.xlsx | XLSX spreadsheet |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
IM/Chat
Section 1: Vendor Information
City: State: ZIP:
Information Services Department Technology Security Assessment County of San Mateo
Technical Support Contact Methods:
This document is to be completed for new or upgraded technology acquisitions, contracts, and projects including all design changes. Please submit all proposals and agreement terms for review to ISD B-1 Review process according to directives in Administrative Memorandum B-1. All questions must be answered fully.
Submitter’s NameSubmitting Department_______________________________________________ ________________________________________________ Phone_________________________________________
Name:
Address:
Corporate Phone #:
(Select all that apply) Phone:
Email:
Web Portal
Technical Support Coverage Hours: 24x7x365 Business Hours M-F 8-5 Pacific
Does the vendor provide a dedicated account manager or representative for escalating problems or incidents?
If yes, please provide name.
Yes No
Does the vendor maintain any formal security policies & Yes No How often is the vendor’s security posture reviewed?
procedures to comply with industry requirements?
Will the vendor provide a copy of their last two security audit, penetration test, and/or vulnerability assessment? Yes No
Does the vendor have any third-party certifications or attestations for its application, such as FedRamp, FIPS 140 -2, FISMA and DIACAP, HIPAA, ISO 27001, PCI DSS, TRUSTe or SOC 1/SOC 2/ SSAE 16/ISAE 3402? If yes, provide certification or attestations.
If cloud solution, does the vendor use a third-party storage solution?
If yes, does the data storage vendor have any third- party certifications or attestations, such as FedRamp, FIPS 140 -2, FISMA and DIACAP, HIPAA, ISO 27001, PCI-DSS, TRUSTe or SOC 1/SOC 2/ SSAE 16/ISAE 3402? If yes, provide certification or attestations
Section 2: Product Information
Yes No
Product Name: No. of Users:
This is an upgrade or renewal for existing technology currently in use in the County
Does the product have technical constraints to the number of concurrent users it can support?
Yes
Location: On-Premise Hosted (Cloud/Off-site) If hosted,GovCloud? Hybrid (On-Premise/Cloud) If hosted,GovCloud?
Product Description and Purpose: Please include information that will identify the function, business process, and the departments/divisions who will use it.
Integration: Does the product integrate or interface with any other existing or planned products or services used either at the County, or with another third-party County vendor? This would include requirements for integration or use of the County’s email System, ServiceNow, or other systems.
Does the vendor use third-party services, such as help desk, integration services, backup services, that would have access to the County’s data?
Please describe.
Does product use open and published APIs?
List all ports/protocols required for any traffic outbound to the Internet or for the application.
Are APIs tested for potential security exploits?
If no, describe what is used to mitigate exploitations and risks.
No
Other
No
Yes
Yes No
No
Yes
Yes No
Yes No
If yes, provide name of third-party data storage vendor
N/A
Escalation procedure for incidents or problems provided? Yes No
No Yes
No N/A
No
N/A
RTOPercentage
Yes
N/A
Yes
Web Services: Is the product 100% web-based? Is the County’s data exposed through web services?
Does the product provide MFA for public access? Does the administrative console require MFA?
Mobile Devices: Does the application provide mobile capabilities? Is the mobile application a requirement for application?
Section 3: Administrative Controls For details on Data Sensitivity and Data Criticality, please see the Section 7 References of this document
Data Sensitivity: Public Internal Confidential* Restricted * * May require NDA
Data Criticality: Useful Important Essential
Data Type: Data is not confidential PII HIPAA/PHI FTI EDD PCI-DSS CJI *
Is system HIPAA compliant? Is system CJI compliant? System meets regulatory requirements?
Configuration and System Hardening: Does the product offer baseline configuration or system hardening tool(s) that can protect the product against confidential data disclosure or service disruption?
**Please provide system configuration diagram and the transport route of data between systems (Required)
Backup and Restore: Does the product offer features to backup and restore user data, configurations, and application code?
Does the product integrate with Rubrik Storage Services and API (the County’s backup platform)?
Is there is a backup process performed by Vendor: Yes No
How often: Encrypted?
Retention period Where stored?
Disaster Recovery: Is the location of the server, if hosted, in an area prone to natural disaster?
Is there a disaster recovery plan in place?
What is the guaranteed uptime?
Data at Termination of Agreement: Will the data be returned? Yes No What assurance is provided for secure and complete removal?
Section 4: Security Controls Has the application been subjected to any breaches? If yes, include separately, enacted steps to mitigate including response and escalation processes
Are there known vulnerabilities? List known vulnerabilities
Are these known vulnerabilities currently being addressed?
Does the vendor use an automated/manual source code analysis tool for secure coding?
. Monitoring and Event Management: Describe how the product can be monitored for performance, reliability, and security. Include how the product reacts to events that are raised during normal operations.
Can the product forward events to a central log repository or System Event Yes No and Incident Management (SEIM) platform?
Patching: Describe how the product is patched and updated. Include how frequently the vendor provides security fixes and updates and how cloud servers will be protected.
If the hardware is onsite, can County engineers apply patches?
If hosted, please provide version, service pack, patches, and how will the server be maintained to the lasted patch level?
No Yes
* System may require DOJ compliance and approval
Yes
Please provide location
Yes No
Yes N/A
No Yes
Yes
RPO
No Yes
Yes No
How often is the disaster recovery plan tested?
Yes N/A
Yes
No Yes Yes No
No Yes
Yes
No Yes No
N/A
N/A
No
N/A
N/A
N/A
No
No
N/A How often is software/system tested for vulnerabilities?
Yes
Yes No
N/A
No
Yes No
Yes
Yes
Yes No
Yes No
Yes No
Anti-Virus Protection: Is anti-virus running?
Malware Protection: Is malware protection running?
Will the product be affected by servers or endpoints that run anti-virus/anti-malware protection? If yes, provide details on what exclusions are required for the product to work effectively.
Employees: Have employees undergone a background check process?
Are employees for this project located in the United States?
Are employees provided required training to handle confidential data, such as CJI, for this engagement?
Will the provider use a subcontractor or 3rd party service provider?
If yes, please attach and provide, for each subcontractor, the security and privacy agreement.
Security Incident Response Plan: Immediate notification to impacted parties?
Identity and Authentication Management:
Does the product provide for, or support identity and authentication integration If yes, with via other credentialing systems or protocols? please specify Note: SAML is the preferred choice for integration with San Mateo County systems *SaaS requires OKTA integration and MFA
Password Management:
How are accounts provisioned and managed (include deprovisioning and removal)?
Does the product provide for password management that meets the County password policy for complexity, expiration, reuse, and lockout? See Section 7 References for more information about San Mateo County’s Password Policy
1. All users have a single account with unique account ID?
2. First time password must be unique and changed upon initial login?
3. Password must be changed every 60 days?
4. Password must have at least 8 characters and 1 character from three of the following: lowercase, uppercase, number, special character?
5. Password cannot be re-used; system is configured to remember las 12 passwords
Does the product provide for password self-reset capability?
How are passwords stored?
Access Management: Does the product allow for privileges to be assigned to both individuals and ‘groups’ of individuals to support the use of ‘Roles’ for access permissions? Please describe method used.
Encryption: Identify and describe whether the product encrypts data during Data-in-transit different states – i.e., at rest, in use, and in transit. Also include credentials Data-in-use
(usernames, passwords, etc.). Include encryption methodology used Data-at-rest
Auditing: Does the product provide a mechanism for auditing system activity and/or reporting of that activity? Examples of auditing include user login/logoff, user actions, data export, and permission changes.
Audit Logs: Does vendor provide audit logs upon request? Will vendor work with County to ensure audit logs can be ingested into the County’s SIEM?
How long are the audit logs stored?
Section 5: Cloud/Hosted Services Data Sovereignty: Does the vendor keep all the data within the United States?
Please provide location(s) where San Mateo County’s data will be stored.
Vendor will consult and advise the County of geographical location of data storage if data will be moved to location other than stated in this document.
Does the cloud solution use industry standard devices?
*Background check confirmation may be requiredYes No
Yes
Yes No
No
What is the time frame?
Yes
Yes
Yes
No
No
No
Yes No
SAML
OAuth
MFA
Active Directory
LDAP
Other
No Yes
Yes
Yes
No
No
No
Yes No
If no, what country? Yes Yes
No No
Credentials
Encrypted? Yes No
No
Yes No
No Yes
Yes No
Yes N/A
Yes
No
Yes No
No
Yes No Yes No
Yes No
Yes No
Yes No
Yes No
Yes No
Yes No
Yes No
Yes No
Tenancy: Describe how San Mateo County data resides with other customer i.e., is the data co-mingled in a single database, or are there separate customer databases?
data in the hosted environment--
Does vendor have the ability logically segment or encrypt data so that the data can be produced for a single tenant only Yes No both application, database, and/or other layers (e.g., Ruby on Rails, Redis Cache, MongoDB)
Hosted Platform: Please describe the vendor’s technology platform in the hosted environment--
Does vendor provide configuration and optimization of cloud services?
Does the vendor provide space availability to avoid resource exhaustion issues?
Network Defenses: Please describe how the vendor's network perimeter is protected, including whether an IPS/IDS and anti-virus system is activated, and if there is a central logging facility for perimeter events
Does the vendor conduct network penetration tests on cloud service infrastructure regularly? Yes No
Service Levels and Incident Response:
What is the service level for this hosted product, and how does the vendor guarantee that level for its customers? Include how the vendor notifies customers of incidents that do not meet service levels
Forensic Analysis: Who would perform a forensic analysis of a breach if one were to occur at the vendor site
Data Loss Events: Has the vendor experienced any data loss incident which required reporting to regulatory authorities in the past 24 months?
Yes No
IP Restrictions: Does the vendor’s hosted site have the capability restrict access to San Mateo County’s public IP address space?
Yes No
Section 6: Support and Maintenance Does the vendor provide proactive system monitoring tool(s) for health check and latency detection that extends to cloud services, as needed?
Is monitoring 24x7
Does the vendor track performance against SLAs?
Is provided vendor support located in the US? If no, provide location
Will vendor require VPN? * Is site-to-site VPN required? * *Vendor required to fill out request form
Does vendor use own remote access tool? *
* Review required; subject to approval of ISD
Are there ports/protocols required to be open for support or VPN access?
List ports and protocols
Does the vendor provide maintenance procedures?
How often are patches/upgrades/maintenance performed on the system?
Will vendor notify County at least 2 weeks in advance for maintenance?
Is there anticipated downtime related to upgrades or maintenance?
Is there a strategy including methodology for upgrading the infrastructure to ensure technology advances and security?
If not, how often?
If yes, identify tool(s) used
If yes, identify remote access tool used
Section 7: References Password Policy
The County of San Mateo’s Information Security Policy requires new technology implementations that use passwords to adhere to the following password requirements:
County of San Mateo Password Requirements
1. All users must have unique account IDs that identifies a single account owner
2. First time password must be unique to an individual, and require change upon initial login
3. The permanent / long term password requires an enforceable change every 60 days
4. The password must enforce a minimum of at least 8 characters, and contain at least one character from three of the following:
a. Lower Case
b. Upper Case
c. Numbers
d. Special Characters
5. Password may not be reused – system is configured to remember last 12 passwords
Data Classification Standards In order to apply the proper security safeguards to digital assets, the County of San Mateo classifies new technology both to a Sensitivity and Criticality class. The following information defines those classification standards and is added as a resource to answering the questions in Section 2, ‘Product Information’.
Section 8: Non-Compliance Please explain area(s) of non-compliance. Provide information as to the services or systems that would be impacted as well as the proposed remediation/mitigation, if any.
NOTE: All non-compliance must file an Information Security Risk Acceptance Form
Yes No
Section 9: Other Documents
Please include any pertinent documents, diagrams of network, and/or data flow architecture. Please note other documents may be requested.
Documents included? Yes No
Network Diagrams * required
Data flow diagram * required
Other security documents
This assessment was prepared by (Print Name)
Signature
Date
Phone
San Mateo County Information Services Department Technology Security Assessment Version 15 20221101
| Submitting Department_______________________________________________ Submitter’s Name________________________________________________ |
| Phone_________________________________________ |
| Section 1: Vendor Information |
| Section 2: Product Information |
| Data Sensitivity: Public Internal Confidential* Restricted * * May require NDA |
| Data Criticality: Useful Important Essential |
| Data Type: Data is not confidential PII HIPAA/PHI FTI EDD PCI-DSS CJI * |
| Section 5: Cloud/Hosted Services |
| Section 6: Support and Maintenance |
| Section 7: References |
| Password Policy |
| The County of San Mateo’s Information Security Policy requires new technology implementations that use passwords to adhere to the following password requirements: |
| 1. All users must have unique account IDs that identifies a single account owner |
| Section 8: Non-Compliance |
| Section 9: Other Documents |
| Submitting Department: |
| Submitters Name: |
| Phone: |
| Name: |
| Corporate Phone: |
| Address: |
| City: |
| State: |
| ZIP: |
| Check BoxPhone: Off |
| Phone: Enter Number Here: |
| Check Box33chat: Off |
| IM/Chat: Enter Method Here: |
| Check Box34email: Off |
| Enter Email Here: |
| Check Box35: Off |
| Enter URL Here: |
| Enter support hours here: Enter support hours here |
| Group1: Off |
| Group2: Off |
| If yes please enter contact information here: If yes, please enter contact information here. |
| How often is vendor security posture reviewed?: |
| Group3: Off |
| Group4: Off |
| If yes please enter certifications or attestations here: If yes, please enter certifications or attestations here. |
| 3rd Party storage: Name of storage vendor |
| If yes please enter 3rd party storage certifications or attestations here: If yes, please enter third-party storage certifications or attestations here. |
| Group5: Off |
| Group6: Off |
| Product Name: |
| Check Box22: Off |
| NumberofUsers: [1-10] |
| Group7: Off |
| Group8: Off |
| Group9: Off |
| Click1: Off |
| Click2: Off |
| Group10: Off |
| Please enter product description and purpse: Please enter product description and purpose. |
| Please describe integration: Please describe integrations here. |
| Group12: Off |
| Please describe third-party services accessing County data: Please describe third-party services accessing County data |
| Group13: Off |
| Group14: Off |
| List all ports/protocols required: List all ports/protocols required. |
| Describe what is used to mitigate exploitations and risks: Describe what is used to mitigate exploitations and risks. |
| Group11: Off |
| Group15: Off |
| Group16: Off |
| Group17: Off |
| Group18: Off |
| Group19: Off |
| Group20: Off |
| Group21: Off |
| Group22: Off |
| Group23: Off |
| Please provide additional detail on configuration and system hardening: Please provide additional detail on configuration and system hardening. |
| Group25: Off |
| Please provide additional detail on backup and restore: Please provide additional detail on backup and restore. |
| Group26: Off |
| Group27: Off |
| How often is backup performed?: Please enter how often backup is performed. |
| What is the retention period?: Please enter retention period. |
| Where is backup stored?: Please enter where the backup is stored. |
| Group28: Off |
| Please provide location: Please provide location. |
| Group29: Off |
| Group30: Off |
| How often recovery plan tested: Please enter times tested. |
| Uptime: Percentage |
| RTO: Hours |
| RPO: Hours |
| What assurance is provided for removal?: Please enter how assurance will be provided that data is completely removed. |
| Group32: Off |
| Group31: Off |
| Please describe steps in mitigation process including escalation and notification: Please describe steps in mitigation process including escalation and notification. |
| Known vulnerabilities?: Please describe known vulnerabilities here. |
| Group33: Off |
| How often test for known vulnerabilities?: Please enter how often. |
| Group34: Off |
| Group35: Off |
| Please enter detail here on monitoring and event management: Please enter detail here on monitoring and event management. |
| Please enter detail here on patching including frequency: Please enter detail here on patching including frequency. |
| Group36: Off |
| If hosted, please enter detail here on version, patching, and how servers are maintained: If hosted, please enter detail here on version, patching, and how servers are maintained. |
| Group37: Off |
| Group24: Off |
| Group39: Off |
| Group40: Off |
| Please provide additional detail on malware protection including exclusions needed for the product to perform with antimalware: Please provide additional detail on malware protection including exclusions needed for the product to perform with anti-malware. |
| Group41: Off |
| Group42: Off |
| If no, what country?: Please provide location. |
| Group43: Off |
| Group44: Off |
| If yes, provide security and privacy agreement: If yes, provide security and privacy agreement for each subcontractor. |
| Notification time frame: Timeframe |
| Group45: Off |
| Group46: Off |
| Check Box27: Off |
| Check Box28: Off |
| Check Box29: Off |
| Check Box30: Off |
| Check Box31: Off |
| Check Box32: Off |
| If other, please indicate: If other, please indicate. |
| How are accounts are provisioned and managed?: Please describe how accounts are provisioned and managed. |
| Group53: Off |
| Group52: Off |
| Group51: Off |
| Group50: Off |
| Group49: Off |
| Group47: Off |
| Describe how passwords are stored: Please describe how passwords are stored. |
| Group54: Off |
| Group48: Off |
| Group55: Off |
| Describe method used for access permissions: Please describe method used for access permissions. |
| Data-in-transit: Describe if data is encrypted in transit. |
| Data-in-use: Describe if data is encrypted in use. |
| Data-at-rest: Describe if data is encrypted at rest. |
| Credentials: Describe if and what credentials types are used. |
| Please describe auditing mechanism: Please describe auditing mechanism here. |
| Group57: Off |
| Group58: Off |
| Group56: Off |
| How long stored?: How long stored? |
| Group59: Off |
| Please enter storage location(s) here: Please enter storage location(s) here. |
| Group60: Off |
| Group61: Off |
| Please enter tenancy details here: Please enter tenancy details here. |
| Please enter details of technology platform: Please enter details of technology platform. |
| Please enter detail of network defenses used: Please enter details of network defenses used. |
| Please enter details of service levels & incident response: Please enter details of service levels and incident response. Include how the County will be notified. |
| Please provide names, roles, and/or third-party organizations who may be involved: Please provide name(s)/role(s), and or third-party organization(s) who may be involved. |
| Please provide additional details of data loss event: If yes, please provide additional details of data loss event. |
| If yes please provide additional details of IP restrictions: If yes, please provide additional details of IP restrictions. |
| If yes identify system monitoring tool(s) used: If yes, identify system monitoring tool(s) used. |
| If not how often?: If not, how often? |
| Vendor support location: Vendor support location. |
| Group72: Off |
| Identify remote access tool(s) used: Identify remote access tool(s) used. |
| List ports and protocols required: List ports and protocols required. |
| Group76: Off |
| Indicate how often system maintenance performed: Indicate how often system maintenance performed. |
| Group62: Off |
| Group63: Off |
| Group64: Off |
| Group65: Off |
| Group66: Off |
| Group67: Off |
| Group68: Off |
| Group69: Off |
| Group70: Off |
| Group71: Off |
| Group74: Off |
| Group75: Off |
| Group77: Off |
| Group78: Off |
| Group79: Off |
| Group73: Off |
| Areas of non-compliance: Please explain all areas of non-compliance as well the mitigation or remediation. |
| This assessment was prepared by Print Name: |
| Date: |
| Phone_3: |
| Group80: Off |
| Group81: Off |
| Group82: Off |
| Group83: Off |
| Group38: Off |
| HIPAASys: Off |
| CJIsys: Off |
| Regsys: Off |
File details come from the government source that posted it. Updated .