What’s new in Cogent: General Agent Comes to Slack

General Agent in Slack (in Early Access)

Security is a team effort, but the context needed to make good decisions often lives inside tools built for security specialists.

With General Agent now available in Slack, anyone with the right access can ask questions about risk and get answers where they are already working.

An engineer can ask whether a newly disclosed vulnerability affects the services they own. An incident responder can investigate an emerging threat with the people coordinating the response. A security leader can ask which risks need attention and why.

This brings security intelligence into the flow of work. Teams can ask follow-up questions, bring the right people into the discussion, and move from a security question to a shared understanding in the same place. 

For security teams, this creates a way to extend their expertise without becoming a bottleneck. For the rest of the organization, it makes security context easier to reach and easier to use in everyday decisions.

Chats started on Slack can be seen and continued in the Agent Chat UI.

Share General Agent chats

Security decisions rarely depend on a single answer. The questions asked, evidence considered, and reasoning behind a recommendation all matter.

General Agent chats can now be shared with teammates through a live, read-only view. Recipients can see the complete conversation without information being copied into a separate document or message.

Chats can also be exported as PDF or HTML for people who need to review the analysis outside Cogent or retain it for reporting.

This makes General Agent chats easier to use as durable work products. Teams can share an investigation with the full context intact, align on its conclusions, and keep a record of the analysis that informed a decision.

Manage risk exceptions with General Agent

Risk exceptions are already part of how teams manage accepted risk in Cogent. Teams can now create and manage them through General Agent as well.

A team can investigate a risk, decide that it should be accepted, and document that decision in the same conversation. They can also return later to update the exception as circumstances change.

Bringing this workflow into General Agent makes risk decisions faster to record and easier to manage. It also keeps the decision close to the analysis that informed it, helping teams preserve a clear understanding of what was accepted and why.

Group findings into remediation work

Cogent automatically generates remediation Work Items for findings. Sometimes, however, security teams identify a specific set of findings that should be addressed together.

Teams can now filter and select findings in the Knowledge Bases, then group them into a new Work Item. This gives teams the flexibility to organize remediation around a shared application, owner, initiative, or other context uncovered during analysis.

Cogent generates remediation guidance for the selected findings, giving the receiving team a clear summary of the risk and the steps needed to address it.

If the work is already being tracked in Jira, ServiceNow, or another connected system, teams can link the Work Item to the existing ticket instead of creating a duplicate. They can also add notes to preserve decisions, investigation details, and handoff context as remediation progresses.

This creates a direct path from ad hoc analysis to coordinated action. Security teams can organize findings around the way they need to be remediated, then hand off the work without recreating context or disrupting workflows already underway.