The following table outlines the versions of OpenSearch Index Manager that are currently supported with security updates:
| Version | Supported | Status | End of Support |
|---|---|---|---|
| 1.0.x | ✅ Yes | Active | TBD |
- Active Support: Receive all security updates and bug fixes
- Maintenance Support: Receive critical security updates only
- End of Life: No longer receiving updates
We take security seriously. If you discover a security vulnerability, please report it responsibly.
Please DO NOT report security vulnerabilities through public GitHub issues.
Instead, please report security vulnerabilities via one of the following methods:
- Email: Send details to security@opensearch.org
- Private GitHub Advisory: Create a private security advisory
When reporting a vulnerability, please include:
- Description: Clear description of the vulnerability
- Steps to Reproduce: Detailed steps to reproduce the issue
- Impact: Assessment of the potential impact
- Affected Versions: Which versions are affected
- Mitigation: Any known workarounds or mitigations
- Proof of Concept: If available, provide a proof of concept (without exploiting real data)
Subject: Security Vulnerability Report - [Brief Description]
## Summary
Brief summary of the vulnerability
## Affected Component
- Plugin Version: [e.g., 1.0.0]
- OpenSearch Dashboards Version: [e.g., 2.19.0]
- Component: [e.g., Document API, UI Component]
## Steps to Reproduce
1. Step one
2. Step two
3. Step three
## Impact
Description of what an attacker could achieve
## Severity Assessment
- [ ] Critical - System compromise, data breach
- [ ] High - Significant security impact
- [ ] Medium - Limited security impact
- [ ] Low - Minor security issue
## Mitigation
Any known workarounds
## Additional Information
Any other relevant details
| Phase | Timeline | Description |
|---|---|---|
| Acknowledgment | Within 48 hours | We acknowledge receipt of your report |
| Initial Assessment | Within 7 days | We provide initial assessment and severity |
| Fix Development | Varies | Depends on severity and complexity |
| Fix Release | Coordinated | Security patch released |
| Public Disclosure | After fix | Public disclosure with credit |
- Acknowledgment: You will receive an acknowledgment within 48 hours
- Assessment: We will assess the report and assign a severity level
- Updates: We will provide regular updates on our progress
- Coordination: We will coordinate disclosure timeline with you
- Credit: We will credit you in the security advisory (unless you prefer anonymity)
Security patches are released as:
- Emergency Releases: For critical vulnerabilities (within 7 days)
- Regular Security Updates: For high/medium severity (next scheduled release)
- Bundled Fixes: For low severity (included in regular releases)
Security updates are announced through:
- GitHub Security Advisories
- GitHub Releases (marked as security releases)
- Mailing list: security-announce@lists.opensearch.org
- Keep Updated: Always use the latest supported version
- Monitor: Subscribe to security advisories
- Network Security: Run OSD behind a firewall/reverse proxy
- Access Control: Use OpenSearch Security for authentication/authorization
- Audit Logging: Enable audit logging for security events
- Input Validation: Always validate user inputs
- Output Encoding: Properly encode outputs to prevent XSS
- Least Privilege: Use minimal required permissions
- Dependencies: Keep dependencies updated
- Security Testing: Include security tests in CI/CD
None currently.
| Advisory | CVE | Severity | Affected Versions | Fixed In |
|---|---|---|---|---|
| None | - | - | - | - |
The plugin implements the following security features:
- All API inputs are validated against schemas
- SQL injection prevention
- XSS prevention through output encoding
- CSRF protection through OSD framework
- Relies on OSD authentication
- Respects OpenSearch Security permissions
- No direct credential storage
- No sensitive data logging
- Error messages don't leak internal details
- Configurable through OSD security settings
The following security tests are run in CI/CD:
- Dependency vulnerability scanning (Dependabot, Snyk)
- Static Application Security Testing (SAST)
- Secret scanning
- Container image scanning
| Test Type | Tool | Frequency |
|---|---|---|
| Dependency Scanning | Dependabot | Continuous |
| SAST | CodeQL | On PR/push |
| Container Scanning | Trivy | On build |
| Secret Detection | GitHub Advanced Security | On push |
This project aims to comply with:
- OWASP Top 10
- CWE Top 25
- OpenSearch Security Best Practices
None currently.
For security-related questions (not vulnerability reports):
- Security Team: security@opensearch.org
- General Inquiries: Discussions
We thank the following security researchers for their responsible disclosures:
- None yet - be the first!
This security policy is subject to change. Last updated: 2024.