testomatio / docs

Documentation for Testomatio
https://docs.testomat.io/
5 stars 1 forks source link

[docs] Create Security page #44

Open poliarush opened 1 year ago

poliarush commented 1 year ago
  1. Introduction

    • Brief overview of the importance of security for the SaaS product.
    • Commitment statement to user and data protection.
  2. Servers Security

    • Data center security measures.
    • Access control to physical infrastructure.
    • Surveillance and monitoring details.
  3. Data Security

    • Data encryption (in transit and at rest).
    • Data backup and redundancy strategies.
    • Data retention and deletion policies.
  4. Access Control

    • Authentication mechanisms (e.g., multi-factor authentication, single sign-on).
    • Role-based access controls.
    • User session management.
  5. Network Security

    • Firewalls and intrusion detection/prevention systems.
    • DDoS protection measures.
    • VPN and private network access details.
  6. Application Security

    • Secure development practices and lifecycle.
    • Regular software updates and patch management.
    • Vulnerability assessment and penetration testing.
  7. Incident Response

    • Procedures for identifying and responding to security incidents.
    • Communication plans for users in the event of a breach.
  8. Third-party Integrations

    • Security vetting of third-party providers.
    • Ensuring third-party components meet security standards.
    • JIRA integration
    • CI\CD intetegration
  9. Compliance and Certifications

    • Overview of industry-specific regulations and standards the SaaS product adheres to (e.g., GDPR, HIPAA, ISO 27001).
    • Details of any security certifications earned.
  10. Employee Training and Awareness

    • Onboarding and continuous training on security best practices.
    • Ensuring a security-first culture.
  11. Security Audits

    • Details of periodic external and internal security audits.
    • Summary of key findings (if transparency is a goal).
  12. User Best Practices

    • Recommendations for users to maintain their security (e.g., password guidelines, ensuring secure connections).
  13. Resources and Tools

    • Offer downloadable resources, guides, or tools that can help users understand or maintain security.
  14. Feedback and Reporting

    • Contact information or methods for users to report potential security concerns.
    • Encourage a proactive security community.
  15. Updates and Changelog

    • Periodic updates on changes made to the security infrastructure or policies.
    • Transparent reporting of past incidents and steps taken to rectify.
  16. Conclusion and Assurance

    • Reiterate the commitment to security.
    • Call to action, if any (like encouraging users to reach out with concerns or to read FAQs).

Also, users requests following questions, we should have answers for such questions on the page:

poliarush commented 1 year ago
poliarush commented 1 year ago

What technical measures protect the data in relation to this asset? Please choose from the following, and/or add your own.

Select all that apply:

  1. Access Control Lists
  2. Anti-Malware
  3. Data Backup
  4. Firewalls
  5. Logging
  6. Mobile Device Management (MDM) Tools
  7. Network Authentication
  8. Regular Software Updates
  9. Other Anonymization
  10. Breach Detection Tools
  11. Encryption
  12. Intrusion Detection Tools
  13. Logical Access Control
  14. Multi-Factor Authentication
  15. Pseudonymization
  16. Vulnerability Detection Tools
poliarush commented 1 year ago

What organisational measures protect the data in relation to the product/service provided by this vendor? Please choose from the following, and/or add your own.

  1. Acceptable Use Policies
  2. Awareness and Training
  3. Business Continuity Plans
  4. Disaster Recovery Plans
  5. Need-To-Know Restrictions
  6. Password Policies
  7. Regular Test Plan
  8. Secure Premises
  9. Supervision
  10. Tabletop Exercises
  11. Other Access Reviews
  12. Background Checks
  13. Data Processing Agreements
  14. Incident Management Plans
  15. Non-Disclosure Agreements
  16. Penetration Tests
  17. Secure Disposal
  18. Segmented Access Control
  19. Surveillance
  20. Vendor Assessments
poliarush commented 1 year ago

I'm undertaking an analysis of Test Management tools and have the following questions on Testomat: a) Does it provide 2FA or something similar in terms of access/logon? b) Where is the data hosted? Is it possible to choose the location? c) Does the Product have ISO27001 Accreditation or similar? If similar what accreditation.

poliarush commented 1 year ago

I just need some additional security documentation for my review. Typically, we look for our vendors to have security documentation to the level of a current SOC2 report, ISO27001 certification, or at least a Security Whitepaper covering industry standards for critical security controls.

Additionally, I can see that you have attached external penetration reports to the vendor form. Are you able to also provide a high level overview confirming actions taken to mitigate the findings within these reports?

poliarush commented 1 year ago
  • Considering Data (either in transit, at rest, or at endpoints), and
  • Confidentiality, Integrity and Availability of services provided

The Answer needs to be provided with either of the 3 options; Yes, No, or Not Applicable, followed by the responses in detail for all the questions.

Meanwhile, if you can share the SOC 2 report, ISO 27001:2013 certificate, and Information Security Policies, to enable us to begin the Vendor Security review process?

poliarush commented 1 year ago