# US 2025/0209158 A1 · Enhanced access threat detection for collaborative software application frameworks

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2025/0209158 A1
- Document ID: US20250209158A1
- Status: Published application
- Kind: A1
- Application number: 18/394,004
- Filed: 2023-12-22
- Published: 2025-06-26
- Earliest claimed: 2023-12-22
- Assignees: Atlassian Pty Ltd.
- Applicants: Atlassian Pty Ltd.
- Inventors: Anthony Knopp; Benjamin Walther; Ryan Crumley
- Web page: https://patentgrep.com/patent/US20250209158A1

## CPC

- G06F 21/554: {involving event detection and direct action}
- G06F 21/54: by adding security routines or objects to programs
- G06F 21/566: {Dynamic detection, i.e. detection performed at run-time, e.g. emulation, suspicious activities}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Techniques for enhanced access threat detection and mitigation for a collaborative software application framework are discussed herein. Embodiments are configured to access event data associated with the collaborative software application framework and identify at least one threat event record object based on the event data that describes an access pattern associated with an entity. Embodiments are also configured to determine, via a threat detection model, that the access pattern associated with the threat event record objects satisfies at least one access threshold parameter. In response to determining that the access pattern satisfies the at least one access threshold parameter, embodiments may generate, via the threat detection model, access threat alerts and cause display of the access threat alerts via an interactive threat detection dashboard.

## Claims

### Claim 1

An apparatus for performing access threat detection for a collaborative software application framework, the apparatus comprising at least one processor and at least one memory including program code, the at least one memory and the program code configured to, with the at least one processor, cause the apparatus to at least:
access event data associated with the collaborative software application framework;
identify at least one threat event record object based on the event data, wherein the at least one threat event record object describes an access pattern associated with an entity, and wherein the access pattern is associated with an access to the collaborative software application framework by the entity;
determine, via at least one threat detection policy employed by a threat detection model, that the access pattern associated with the at least one threat event record object satisfies at least one access threshold parameter; and
in response to determining that the access pattern associated with the at least one threat event record object satisfies the at least one access threshold parameter:
generate, based on the at least one threat detection policy employed by the threat detection model, at least one access threat alert associated with the collaborative software application framework; and
cause display of the at least one access threat alert via an interactive threat detection dashboard rendered on a client computing device associated with the collaborative software application framework.

### Claim 2 (depends on 1)

The apparatus of claim 1, wherein the at least one threat detection policy is a first threat detection policy of a plurality of threat detection policies associated with the threat detection model,
wherein the plurality of threat detection policies is associated with a plurality of clients, wherein the plurality of clients is associated with a plurality of collaborative software application frameworks, and
wherein each threat detection policy of the plurality of threat detection policies is associated with one or more respective access threshold parameters.

### Claim 3 (depends on 2)

The apparatus of claim 2, wherein the one or more respective access threshold parameters associated with the first threat detection policy are configured by a first client of the plurality of clients via the interactive threat detection dashboard.

### Claim 4 (depends on 2)

The apparatus of claim 2, wherein the at least one threat event record object is a first threat event record object of a batch of threat event record objects,
wherein the batch of threat event record objects is associated with the plurality of collaborative software application frameworks, and
wherein the threat detection model is applied to the batch of threat event record objects.

### Claim 5 (depends on 1)

The apparatus of claim 1, wherein the program code is configured to, with the at least one processor, further cause the apparatus to:
generate, via a threat detection data service and based at least in part on at least one access threat detection job initiated by a threat detection job service, one or more dynamic table objects, wherein the one or more dynamic table objects generated based at least in part on metadata associated with the event data; and
generate, via the threat detection data service and based at least in part on one or more database commands initiated by the threat detection job service, the at least one threat event record object based on the event data associated with the one or more dynamic table objects, wherein the one or more database commands are initiated based at least in part on the at least one access threat detection job.

### Claim 6 (depends on 5)

The apparatus of claim 5, wherein the threat detection job service is configured to initiate the at least one access threat detection job based on a predefined periodicity of time.

### Claim 7 (depends on 1)

The apparatus of claim 1, wherein the at least one threat detection policy employed by the threat detection model is generated based at least in part on at least one portion of client input data received via the interactive threat detection dashboard.

### Claim 8 (depends on 1)

The apparatus of claim 1, wherein the at least one access threshold parameter is a first access threshold parameter of a plurality of access threshold parameters,
wherein the plurality of access threshold parameters comprises at least one of a view count, view duration, modification count, modification amount, export count, export amount, import count, or import amount associated with at least one portion of content data associated with the collaborative software application framework; and
wherein each access threshold parameter of the plurality of access threshold parameters is associated with a predetermined time interval.

### Claim 9 (depends on 1)

The apparatus of claim 1, wherein the at least one access threat alert is associated with at least one of an alert severity, an alert identifier, an access threat alert type, an alert description, an alert data source, an alert timestamp, an alert responder profile, an alert mitigation status, or an alert mitigation ticket.

### Claim 10 (depends on 1)

The apparatus of claim 1, wherein the at least one access threat alert is associated with a respective access threat alert type of a plurality of access threat alert types, and
wherein the plurality of access threat alert types comprise at least one of a collaborative document alert type, an issue tracking alert type, a suspicious search alert type, an administrative account alert type, or a code repository alert type.

### Claim 11 (depends on 10)

The apparatus of claim 10, wherein the collaborative document alert type is associated with at least one of an unusual page activity alert associated with a respective collaborative document, a mass page export alert associated with one or more respective collaborative documents, a restricted document access alert, an unauthorized user access alert, or an alert associated with a high volume of collaborative document content being made public.

### Claim 12 (depends on 10)

The apparatus of claim 10, wherein the issue tracking alert type is associated with at least one of a mass issue tracking object export alert or unusual issue activity associated with one or more issue tracking objects.

### Claim 13 (depends on 10)

The apparatus of claim 10, wherein the administrative account alert type is associated with at least one of an administrative account change alert, an external access granted alert, a security assertion markup language (SAML) alert, an administrative account application programming interface (API) token change alert, or alert associated with a connection of an administrative account to an external third-party service.

### Claim 14 (depends on 10)

The apparatus of claim 10, wherein the code repository alert type is associated with at least one of a mass code repository clone alert, a mass code repository export alert, or a mass code repository commit alert.

### Claim 15 (depends on 1)

The apparatus of claim 1, wherein the at least one access threat alert is associated with a threat detection payload, wherein the threat detection payload is associated with at least one portion of content data of the collaborative software application framework, and wherein the at least one portion of content data corresponds to an access threat alert type associated with the at least one access threat alert.

### Claim 16

A computer program product for performing threat detection for a collaborative software application framework, the computer program product comprising at least one non-transitory computer-readable storage medium having computer-readable program code portions stored therein, the computer-readable program code portions configured to:
access event data associated with the collaborative software application framework;
identify at least one threat event record object based on the event data, wherein the at least one threat event record object describes an access pattern associated with an entity, and wherein the access pattern is associated with an access to the collaborative software application framework by the entity;
determine, via at least one threat detection policy employed by a threat detection model, that the access pattern associated with the at least one threat event record object satisfies at least one access threshold parameter; and
in response to determining that the access pattern associated with the at least one threat event record object satisfies the at least one access threshold parameter:
generate, based on the at least one threat detection policy employed by the threat detection model, at least one access threat alert associated with the collaborative software application framework; and
cause display of the at least one access threat alert via an interactive threat detection dashboard rendered on a client computing device associated with the collaborative software application framework.

### Claim 17

A computer-implemented method for performing threat detection for a collaborative software application framework, the computer-implemented method comprising:
accessing event data associated with the collaborative software application framework;
identifying at least one threat event record object based on the event data, wherein the at least one threat event record object describes an access pattern associated with an entity, and wherein the access pattern is associated with an access to the collaborative software application framework by the entity;
determine, via at least one threat detection policy employed by a threat detection model, that the access pattern associated with the at least one threat event record object satisfies at least one access threshold parameter; and
in response to determining that the access pattern associated with the at least one threat event record object satisfies the at least one access threshold parameter:
generate, based on the at least one threat detection policy employed by the threat detection model, at least one access threat alert associated with the collaborative software application framework; and
cause display of the at least one access threat alert via an interactive threat detection dashboard rendered on a client computing device associated with the collaborative software application framework.

### Claim 18 (depends on 17)

The computer-implemented method of claim 17, wherein the at least one threat detection policy is a first threat detection policy of a plurality of threat detection policies associated with the threat detection model,
wherein the plurality of threat detection policies is associated with a plurality of clients, wherein the plurality of clients is associated with a plurality of collaborative software application frameworks, and
wherein each threat detection policy of the plurality of threat detection policies is associated with one or more respective access threshold parameters.

### Claim 19 (depends on 18)

The computer-implemented method of claim 18, wherein the one or more respective access threshold parameters associated with the first threat detection policy are configured by a first client of the plurality of clients via the interactive threat detection dashboard.

### Claim 20 (depends on 18)

The computer-implemented method of claim 18, wherein the at least one threat event record object is a first threat event record object of a batch of threat event record objects,
wherein the batch of threat event record objects is associated with the plurality of collaborative software application frameworks, and
wherein the threat detection model is applied to the batch of threat event record objects.
