Skip to content

Security: jetnet/OpensearchDashboardCRUD

Security

SECURITY.md

Security Policy

Supported Versions

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

Version Support Policy

  • Active Support: Receive all security updates and bug fixes
  • Maintenance Support: Receive critical security updates only
  • End of Life: No longer receiving updates

Reporting a Vulnerability

We take security seriously. If you discover a security vulnerability, please report it responsibly.

How to Report

Please DO NOT report security vulnerabilities through public GitHub issues.

Instead, please report security vulnerabilities via one of the following methods:

  1. Email: Send details to security@opensearch.org
  2. Private GitHub Advisory: Create a private security advisory

What to Include

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)

Example Report Template

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

Response Process

Timeline

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

What to Expect

  1. Acknowledgment: You will receive an acknowledgment within 48 hours
  2. Assessment: We will assess the report and assign a severity level
  3. Updates: We will provide regular updates on our progress
  4. Coordination: We will coordinate disclosure timeline with you
  5. Credit: We will credit you in the security advisory (unless you prefer anonymity)

Security Update Process

Security Patch Releases

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)

Notification Channels

Security updates are announced through:

Security Best Practices

For Administrators

  1. Keep Updated: Always use the latest supported version
  2. Monitor: Subscribe to security advisories
  3. Network Security: Run OSD behind a firewall/reverse proxy
  4. Access Control: Use OpenSearch Security for authentication/authorization
  5. Audit Logging: Enable audit logging for security events

For Developers

  1. Input Validation: Always validate user inputs
  2. Output Encoding: Properly encode outputs to prevent XSS
  3. Least Privilege: Use minimal required permissions
  4. Dependencies: Keep dependencies updated
  5. Security Testing: Include security tests in CI/CD

Known Vulnerabilities

Active Advisories

None currently.

Past Advisories

Advisory CVE Severity Affected Versions Fixed In
None - - - -

Security Features

The plugin implements the following security features:

Input Validation

  • All API inputs are validated against schemas
  • SQL injection prevention
  • XSS prevention through output encoding
  • CSRF protection through OSD framework

Authentication & Authorization

  • Relies on OSD authentication
  • Respects OpenSearch Security permissions
  • No direct credential storage

Data Protection

  • No sensitive data logging
  • Error messages don't leak internal details
  • Configurable through OSD security settings

Security Testing

Automated Security Testing

The following security tests are run in CI/CD:

  • Dependency vulnerability scanning (Dependabot, Snyk)
  • Static Application Security Testing (SAST)
  • Secret scanning
  • Container image scanning

Security Test Coverage

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

Compliance

Standards

This project aims to comply with:

Certifications

None currently.

Contact

For security-related questions (not vulnerability reports):

Acknowledgments

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.

There aren't any published security advisories