Analyst Agent security
Updated 6 November 2026
/agent-integrations/analyst-agent/security
Analyst Agent security
How the Analyst Agent handles access, hosting, storage, logging and sign-in, for security and IT review. The MCP connector reads the same TechWolf data but runs no AI model at TechWolf, and has its own pages: MCP connector security.
Key attributes
Access follows the Console Each person needs the TechWolf Agent role in the TechWolf Console, and the agent answers from the data that person can see there, plus TechWolf's Market Intelligence data. |
Hosting by geography TechWolf hosts the agent on Amazon Web Services (AWS), in the geography that holds the organisation's TechWolf data. It runs in the EU and the US: organisations whose data is held in Canada can use the MCP connector instead. In Microsoft 365 Copilot, messages first pass through Azure Bot Service and Azure Front Door in TechWolf's own Azure tenant. |
No connection to HR systems The agent reads the organisation's data from TechWolf and doesn't connect to the organisation's HR system. Through Microsoft 365 Copilot or another AI tool, TechWolf gets no access to the organisation's files or email: it receives only what a person or the AI tool sends to the agent, such as a question or a search. |
Training Amazon Bedrock does not use the Analyst Agent's prompts or answers to train models. |
Certifications and compliance TechWolf holds ISO/IEC 27001 and ISO/IEC 42001 certifications and SOC 2 Type 1 and Type 2 reports, complies with the GDPR, and sets out its processing activities in its Data Processing Agreement (DPA). The certificates and reports are available on request from its trust centre at trust.techwolf.ai. |
Contacts Security questions: security@techwolf.ai. Data protection and privacy questions: TechWolf's DPO office at privacy@techwolf.ai. |
How it works
| Analyst Agent | |
|---|---|
| AI model | Run by TechWolf on Amazon Bedrock, with Anthropic's Claude models. Bedrock may run a request in any AWS region of the organisation's geography, never outside it. |
| What TechWolf stores | Each person's conversations, including the data the agent read and uploaded files, in the agent's region. Each person's name and email address. |
| What is logged | Per question: who asked, when, which tools ran, duration and cost, without the text. The agent's requests to TechWolf's data service are logged too, including search terms. The Amazon Bedrock invocation log keeps the full prompts, including the data the agent read, and the answers. |
| How long it is kept | Conversations and uploaded files: until the organisation asks TechWolf to delete them. Runtime logs and the Bedrock invocation log: 30 days, in the same geography. The usage record of each question is kept for the organisation's usage reports. |
| Who at TechWolf can see it | Authorised TechWolf staff, through an internal review tool, and the product team, to improve the agent. |
| Employees in answers | Under the identifiers the organisation loaded into TechWolf, with names where it loaded them. |
| Changes to data | Proposed role redesigns, which wait for review, and temporary custom tasks. |
| Sign-in | As for the Console, or with a Microsoft account in Copilot. In the Console, the model gets an internal user identifier. In Microsoft 365 Copilot it can get the person's sign-in identifier, which can contain their email address. It never gets a password or key. |
| Service providers | AWS, including Amazon Bedrock; Auth0, for sign-in; PostHog, in the US, for product analytics without question or answer text; Sentry, for error reports. In Copilot, also Microsoft. |
Uploads, tools and changes to data
- Uploads. People can upload files, such as a list of jobs, in the Console, not in Copilot. Removing a file takes it out of the conversation, but TechWolf keeps it with the conversation.
- Tools. The agent has no web access: its tools reach only TechWolf's data service and a calculation sandbox without network access, so an instruction hidden in an uploaded file or in data cannot make the agent's tools send data out of TechWolf.
- Role redesign. The agent is instructed to send a finished role redesign to the Console only when a person asks, as task and skill changes to one job. Only people allowed to edit and submit job skill and job task changes in the Console can send them, and nothing reaches the job until a reviewer approves the changes and a publisher publishes them.
- Custom tasks. To match a future job profile against existing jobs, the agent can create a temporary custom task for work that has no task yet. It is instructed to remove the task again in the same answer.
Microsoft 365 Copilot
In Microsoft 365 Copilot, TechWolf uses and keeps only the verified email address and the Entra tenant identifier from a person's Microsoft sign-in. The admin consent covers sign-in only: TechWolf reads no directory, mailbox or file content.