Ensure Athena named queries do not contain sensitive data
Saved named queries should not contain credentials, PII, or sensitive filters that could expose information.
Security Impact
Named queries are visible to all users with workgroup access, potentially exposing sensitive information.
How to Remediate
Review all named queries for hardcoded sensitive data. Use parameterized queries or environment-specific workgroups instead.
Affected Resources
Compliance Frameworks
How TigerGate Helps
TigerGate continuously monitors your AWS environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:
- Continuous Scanning
Automatically scans all Amazon Athena resources across your AWS accounts every hour
- Instant Alerts
Get notified via Slack, email, or webhooks when this misconfiguration is detected
- One-Click Remediation
Fix this issue directly from the TigerGate dashboard with our guided remediation
- Compliance Evidence
Automatically collect audit evidence for Data Protection, GDPR compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-athena-9
- Service
- Amazon Athena
- Category
- Data Protection
- Severity
- MEDIUM
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free TrialRelated Amazon Athena Checks
View all checksEnsure Athena workgroup enforces query result encryption
Ensure Athena workgroup enforces minimum encryption configuration
Ensure Athena workgroup has CloudWatch metrics enabled
Ensure Athena query results have lifecycle policies for cost control
Ensure Athena databases use encrypted data sources