Attachment_D_-_Vendor_IT_Security_Questionnaire.xlsx
XLSX spreadsheet 14 KB Posted
- Solicitation number
- PR8582
- Issued by
- Florida
About this file
This is an IT Security Questionnaire document associated with an Electric Vehicle Supply Equipment (EVSE) Maintenance Services contract opportunity in Florida. The questionnaire is designed to assess the security posture of a third-party software application that will serve as the comprehensive platform for the EVSE maintenance services pilot program. The selected vendor must demonstrate compliance across seven major security domains: application security practices (including secure software development lifecycle, vulnerability management, and authentication/authorization controls), data security and privacy measures, application infrastructure and hosting security, incident management and monitoring capabilities, compliance with regulatory standards, and risk assessment procedures with continuous improvement protocols.
The questionnaire requires vendors to detail their development lifecycle practices, including whether security requirements are incorporated during design phases and if static and dynamic application security testing is performed. Vendors must also address their vulnerability management programs, patch application frequencies, penetration testing practices, and cybersecurity due diligence for third-party dependencies. Critical sections address data encryption standards (such as AES-256 and TLS 1.2+), multi-factor authentication support, role-based access controls, data retention and disposal policies, logging and monitoring capabilities with minimum 90-day retention periods, and compliance certifications such as ISO 27001, SOC 2, NIST, and PCI DSS. Additionally, vendors must disclose any known security issues, describe their formal incident response plans with breach notification timelines, confirm regular security training for employees and contractors, and provide documentation of formal risk assessments and penetration testing frequencies for their software platform.
View the file
Other files
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
IT Security Questionnaire
| Vendor IT Security Questionnaire |
| Application Name: |
| Application Developer / Reseller: |
| Application version: |
1. Application Security Practices Response Yes/ No /Partial Partial - Please Explain
| 1.1 Development Lifecycle |
| Does the third party follow a secure software development lifecycle (SDLC)? |
| Are security requirements incorporated during the design phase of the SDLC? |
| Are security reviews conducted at each phase of the development process? |
| Is static and dynamic application security testing (SAST/DAST) performed during development? |
| Does the application undergo regular security code reviews? |
| 1.2 Vulnerability Management |
| Does the third party have a vulnerability management program in place? |
| How frequently are security patches and updates applied to the application? |
| What is the process for addressing security vulnerabilities reported by third parties, users, or automated tools? |
| How are software vulnerabilities tracked and remediated (e.g., CVE reporting, timelines)? |
| Is your product penetration tested regularly by internal or third-party professionals? |
| Do you perform cybersecurity due diligence for third-party libraries, APIs, and cloud services used in your software? |
| Are third-party dependencies tracked, evaluated for security risk, and updated regularly? |
| 1.3 Authentication and Authorization |
| Does the application support multi-factor authentication (MFA)? |
| Does the application utilize role-based access control (RBAC) to ensure least-privilege access? |
| Are credentials stored using strong cryptographic algorithms (e.g., salted hashes)? |
| Does the application support Single Sign-On (SSO)? |
| Are password policies enforced (e.g., complexity, expiration)? |
| Is access to the software environment and data governed by role-based access controls and MFA? |
2. Data Security and Privacy
| 2.1 Data Encryption |
| Is sensitive data encrypted at rest and in transit? |
| What encryption standards are used (e.g., AES-256, TLS 1.2+)? |
| Is key management performed according to industry standards (e.g., hardware security modules)? |
| 2.2 Data Retention and Disposal |
| Does the third party have a data retention policy in place? |
| How is sensitive data securely disposed of when no longer required? |
| 2.3 Third-Party Data Sharing |
| Does the application share data with any external third parties? |
| If yes, is data sharing governed by contracts or data protection agreements (e.g., GDPR, CCPA)? |
| Are sensitive data exchanges encrypted? |
3. Application Infrastructure and Hosting Security
| 3.1 Environment Security |
| Where is the application development hosted (e.g., cloud, on-premise, hybrid)? |
| Is the hosting environment hardened according to industry best practices? |
| Are servers regularly patched and updated? |
| Is the application development hosted in a segregated network or isolated from other systems? |
| 3.2 Backup and Recovery |
| Are regular backups taken of critical application data and configurations? |
| Are backups encrypted and stored in a secure location? |
| Does the application have a documented disaster recovery plan (DRP)? |
| Has the application undergone disaster recovery testing in the last 12 months? |
4. Incident Management and Monitoring
| 4.1 Security Incident Management |
| Does the third party have a formal incident response plan (IRP) in place? |
| Are security incidents regularly reported and tracked? |
| In the event of a security breach, how quickly will the third party notify affected customers? |
| Is there a documented, tested incident response plan specific to the software you deliver? |
| 4.2 Logging and Monitoring |
| Are security logs generated for critical application events (e.g., login attempts, data access)? |
| Are logs monitored and reviewed regularly for suspicious activities? |
| Are logs retained for a minimum of 90 days? |
| Are security logs protected from unauthorized access or modification? |
| Do you monitor your product and infrastructure for anomalous or unauthorized behavior? |
5. Compliance and Regulatory Requirements
| 5.1 Compliance Standards |
| Does the application meet any industry security standards or frameworks? (e.g., ISO 27001, SOC 2, NIST, PCI DSS) |
| Please list the relevant compliance certifications the application holds: |
| 5.2 Data Protection Laws |
| Is the application compliant with data protection regulations such as GDPR, CCPA, HIPAA, etc.? |
| Does the third party provide a data processing agreement (DPA) or similar legal document? |
6. Risk Assessment and Continuous Improvement
| 6.1 Risk Assessment |
| Does the third party conduct regular security risk assessments of the application? |
| Are third-party security assessments, such as penetration testing or external audits, conducted periodically? |
| When were the last third-party security assessments performed? |
| 6.2 Security Training and Awareness |
| Do employees involved in the development and operation of the application receive regular security training? |
| Are third-party developers and contractors required to undergo security awareness training? |
7. Additional Information
| Are there any known security issues, vulnerabilities, or challenges with the application? |
| Are there any additional security measures or protocols that the third party employs? |
| Do you maintain a documented information security program endorsed by executive leadership? |
| How often do you perform formal risk assessments related to your software product and delivery? |
| How often do you perform formal penetration testing to your software product? |
| Signature: |
| By completing this questionnaire, you acknowledge that the information provided is accurate to the best of your knowledge and will be used to assess the security posture of the third-party application. |
| Name: |
| Position: |
| Date: |
File details come from the government source that posted it. Updated .