Skip to content

Security: Text-It/TextItCLI

Security

docs/SECURITY.md

πŸ”’ TextIt Security Policy

Last Updated: August 17, 2025 | Version 3.0.0

View Change History | Security Advisories

πŸ›‘οΈ Security at TextIt

At TextIt Corporation, we prioritize the security of our software and the protection of our users' data. This document outlines our security policies, procedures, and best practices for maintaining a secure environment.

πŸ“‹ Table of Contents

  1. Supported Versions
  2. Reporting Security Issues
  3. Security Response Process
  4. Security Measures
  5. Secure Development
  6. Compliance & Certifications
  7. Security Best Practices
  8. Incident Response
  9. Contact Information

πŸš€ Supported Versions

Version Status End of Support
3.0.x βœ… Active December 31, 2026
2.0.x ⚠️ Maintenance December 31, 2025
< 2.0 ❌ EOL Not supported

Note: Critical security patches may be backported to maintenance versions for a limited time.

🚨 Reporting Vulnerabilities

We take all security vulnerabilities seriously. If you've discovered a security issue in TextIt, we appreciate your help in disclosing it to us in a responsible manner.

πŸ” How to Report

  1. Do not publicly disclose the vulnerability
  2. Submit your report via one of these methods:

πŸ“‹ Report Requirements

For efficient processing, please include:

  • TextIt version affected

  • Steps to reproduce the issue

  • Impact of the vulnerability

  • Any proof-of-concept code (if available)

  • Your contact information

  • Detailed description of the vulnerability

  • Step-by-step reproduction instructions

  • Impact assessment

  • Any proof-of-concept code (if available)

  • Your contact information

  • Preferred method for acknowledgment

🎯 Our Commitment

  • Response Time: Initial response within 24 hours
  • Assessment: Triage within 3 business days
  • Resolution: Fix timeline based on severity
  • Recognition: Public acknowledgment (unless requested otherwise)

🚦 Security Response Process

  1. Acknowledgement: You'll receive a confirmation of your report
  2. Validation: Our security team verifies the vulnerability
  3. Prioritization: Based on CVSS score and impact
  4. Remediation: Development of a fix
  5. Testing: Security and regression testing
  6. Release: Deployment of the security update
  7. Disclosure: Public announcement (coordinated with reporter)

πŸ›‘οΈ Security Measures

πŸ” Authentication & Access Control

  • Multi-Factor Authentication (MFA)

    • Time-based One-Time Passwords (TOTP)
    • Biometric authentication
    • Hardware security keys (FIDO2/U2F)
    • SMS/Email OTP fallback
  • Password Security

    • Argon2id with appropriate work factors
    • Minimum 12-character requirement
    • Password strength meter
    • Breached password detection
    • Passwordless authentication options

πŸ”’ Data Protection

  • Encryption

    • AES-256-GCM for data at rest
    • TLS 1.3 for data in transit
    • Field-level encryption for sensitive data
    • Secure key management with AWS KMS
  • Database Security

    • Row-level security
    • Dynamic data masking
    • Automated backups with encryption
    • Regular security patching

πŸ›‘οΈ Application Security

  • Input Validation

    • Strict type checking
    • Input sanitization
    • Content Security Policy (CSP)
    • Anti-CSRF tokens
  • API Security

    • OAuth 2.1 with PKCE
    • Rate limiting and throttling
    • Request validation
    • Comprehensive logging

πŸ—οΈ Secure Development

πŸ› οΈ Development Practices

  • Secure coding standards (OWASP ASVS)
  • Automated security testing in CI/CD
  • Dependency scanning (Snyk, Dependabot)
  • Regular security training for developers
  • Threat modeling for new features

πŸ§ͺ Security Testing

  • Static Application Security Testing (SAST)
  • Dynamic Application Security Testing (DAST)
  • Interactive Application Security Testing (IAST)
  • Penetration testing (quarterly)
  • Bug bounty program

πŸ“œ Compliance & Certifications

  • GDPR compliant
  • CCPA compliant
  • SOC 2 Type II (in progress)
  • ISO 27001 (target Q4 2025)
  • Regular third-party security audits

πŸ›‘οΈ Security Best Practices

πŸ”„ Regular Updates

  • Monthly security patches
  • Dependency updates (automated)
  • Infrastructure as Code (IaC) scanning
  • Container vulnerability scanning

πŸ” Monitoring & Logging

  • SIEM integration
  • Real-time alerting
  • Anomaly detection
  • 90-day log retention

🚨 Incident Response

Our incident response team is available 24/7 to address security incidents. In case of a security breach:

  1. Containment: Isolate affected systems
  2. Eradication: Remove the threat
  3. Recovery: Restore services
  4. Post-Mortem: Document and learn

πŸ“ž Contact Information

For security-related inquiries:

🀝 Responsible Disclosure

We follow responsible disclosure guidelines and will work with security researchers to validate and address reported vulnerabilities. We ask that you:

  • Allow us a reasonable time to address the issue
  • Not exploit the vulnerability or access/modify user data
  • Keep the issue confidential until we've had time to address it

πŸ“œ License

This Security Policy is licensed under the Creative Commons Attribution 4.0 International License.


Β© 2025 TextIt Corporation. All rights reserved.

123 Tech Park, Near Sola Road, S.G. Highway, Ahmedabad, Gujarat 380061, India

- TOTP support - Biometric authentication - Security Monitoring: - Audit logging - Security event tracking - Regular security audits

Security Updates

Security updates will be announced through:

  1. GitHub security advisories
  2. Release notes
  3. The official TextIt communication channels

Security Best Practices for Users

We recommend that users of TextIt follow these security best practices:

  1. Use strong, unique passwords
  2. Keep your client software updated to the latest version
  3. Be cautious about the information you share through the platform
  4. Report any suspicious activity immediately

Thank you for helping keep TextIt and our users safe!

There aren't any published security advisories