This document is provided for informational purposes only. It represents the current product offerings and practices from Amazon Web Services (AWS) as of the date of issue of this document, which are subject to change without notice. Customers are responsible for making their own independent assessment of the information in this document and any use of AWS products or services, each of which is provided “as is” without warranty of any kind, whether express or implied. This document does not create any warranties, representations, contractual commitments, conditions, or assurances from AWS, its affiliates, suppliers, or licensors. The responsibilities and liabilities of AWS to its customers are controlled by AWS agreements, and this document is not part of, nor does it modify, any agreement between AWS and its customers.
© 2024 Amazon Web Services, Inc. or its affiliates. All Rights Reserved. This work is licensed under a Creative Commons Attribution 4.0 International License.
This AWS Content is provided subject to the terms of the AWS Customer Agreement available at http://aws.amazon.com/agreement or other written agreement between the Customer and either Amazon Web Services, Inc. or Amazon Web Services EMEA SARL or both.
Author: Author Name
Approver: Approver Name
Last Date Approved:
This playbook outlines example processes and queries to investigate security events involving Amazon Q.
This playbook references and integrates, where possible, with Prowler which is a command line tool that helps you with AWS security assessment, auditing, hardening and incident response.
Throughout the execution of the playbook, focus on the *desired outcomes*, taking notes for enhancement of incident response capabilities.
AWS Cloud Adoption Framework Security Perspective

I need a business decision on when EC2 forensics should be conductedWho is monitoring the logs/alerts, receiving them and acting upon each?Who gets notified when an alert is discovered?When do public relations and legal get involved in the process?When would you reach out to AWS Support for help?Amazon Q is compromised of multiple components/services:
The event names listed in the table below are a quick reference for types of events typically found in CloudTrail during the investigation of a security event involving Q. Of those listed in the table, the most common event names that are logged during normal model usage are:
GetConversationStartConversationGetIndexListRetrieversGetApplications| Event Names | Description |
|---|---|
| General Permissions | — |
GetConversation |
Grants permission to get individual messages associated with a specific conversation with Amazon Q |
GetTroubleshootingResults |
Grants permission to get troubleshooting results with Amazon Q |
SendMessage |
Grants permission to send a message to Amazon Q |
StartConversation |
Grants permission to start a conversation with Amazon Q |
StartTroubleshootingAnalysis |
StartTroubleshootingAnalysis Grants permission to start a troubleshooting analysis with Amazon Q |
StartTroubleshootingResolutionExplanation |
Grants permission to start a troubleshooting resolution explanation with Amazon Q |
| Creating an application | ——– |
CreateApplication |
Grants permission to create an application |
DeleteApplication |
Grants permission to delete an application |
GetApplication |
Grants permission to get an application |
ListApplications |
Grants permission to list the applications |
UpdateApplication |
Grants permission to update an Application |
| Creating an index | ——– |
CreateIndex |
Grants permission to create an index for a given application |
DeleteIndex |
Grants permission to delete an index |
GetIndex |
Grants permission to get an index |
ListIndices |
Grants permission to list the indices of an application |
UpdateIndex |
Grants permission to update an index |
| Creating a retriever | ——– |
CreateRetriever |
Grants permission to create a retriever for a given application |
DeleteRetriever |
Grants permission to delete a retriever |
GetRetriever |
Grants permission to get a retriever |
ListRetrievers |
Grants permission to list the retrievers of an application |
UpdateRetriever |
Grants permission to update a Retriever |
| Connecting data sources | ——– |
CreateDataSource |
Grants permission to create a data source for a given application and index |
DeleteDataSource |
Grants permission to delete a DataSource |
GetDataSource |
Grants permission to get a data source |
ListDataSources |
Grants permission to list the data sources of an application and an index |
UpdateDataSource |
Grants permission to update a DataSource |
StartDataSourceSyncJobs |
Grants permission to start Data Source sync job |
StopDataSourceSyncJobs |
Grants permission to stop Data Source sync job |
ListDataSourceSyncJobs |
Grants permission to get Data Source sync job history |
| Uploading documents | ——– |
BatchPutDocument |
Grants permission to batch put document |
BatchDeleteDocument |
Grants permission to batch delete document |
| Chat and conversation management | ——– |
Chat |
Grants permission to chat using an application |
ChatSync |
Grants permission to chat synchronously using an application |
DeleteConversation |
Grants permission to delete a conversation |
ListConversations |
Grants permission to list all conversations for an application |
ListMessages |
Grants permission to list all messages |
| User and group management | ——– |
CreateUser |
Grants permission to create a user |
DeleteUser |
Grants permission to delete a user |
GetUser |
Grants permission to get a user |
UpdateUser |
Grants permission to update a user |
PutGroup |
Grants permission to put a group of users |
DeleteGroup |
Grants permission to delete a group |
GetGroup |
Grants permission to get a group |
ListGroups |
Grants permission to list groups |
| Plugins | ——– |
CreatePlugin |
Grants permission to create a plugin for a given application |
DeletePlugin |
Grants permission to delete a plugin |
GetPlugin |
Grants permission to get a plugin |
UpdatePlugin |
Grants permission to update a plugin |
| **Admin controls and guardrails ** | ——– |
UpdateChatControlsConfiguration |
Grants permission to update chat controls configuration for an application |
DeleteChatControlsConfiguration |
Grants permission to delete chat controls configuration for an application |
GetChatControlsConfiguration |
Grants permission to get chat controls configuration for an application |
By default, CloudTrail doesn’t log data events. The following shows the Amazon Q API operations logged to CloudTrail as data events. The Data event type (console) column shows the appropriate selection in the CloudTrail console. The Amazon Q resource types column shows the resources.type value that you would specify to log data events for the resource. More information is available in the Q User Guide.
Amazon Q Business Applications: AWS::QBusiness::Application
Amazon Q Business Data Resource: AWS::QBusiness::DataSource
Amazon Q Business Index: AWS::QBusiness::Index
In the event of an incident, in addition to investigating the indicators of compromise, threat actor, timeframe, etc., here are some additional questions to consider once it has been confirmed that this is an incident relating to Amazon Q resources:
AmazonQFullAccess managed policy provides full access to enable interactions with Amazon Q. All Admins and power users have access by default but for other users and roles, customer will need to attach the AWS Q managed policy. Permissions can be restricted based on Amazon Q actions.This is a place to add items specific to your company that do not necessarilly need "fixing", but are important to know when executing this playbook in tandem with operational and business requirements.