Jump to Content
Secberus DocumentationHomeGuidesTerms & ConceptsAPI DocumentationPush APIRelease NotesStatus
HomeGuidesAPI ReferenceRelease Notes
v12.12.2

HomeGuidesTerms & ConceptsAPI DocumentationPush APIRelease NotesStatusSecberus Documentation
Guides
v12.12.2
Authentication
All
Pages
Start typing to search…

Getting Started

  • What is Secberus?
  • Data Collection Process
  • Terms and Concepts

Support

  • Support

Platform Setup

  • Organizations
  • User Management
    • Custom Roles
    • Available Attributes
    • API Action Permissions
  • AWS Data Source
    • AWS IAM Role
    • AWS IAM User
    • AWS Resources Collected
    • Required Permissions
  • Azure Data Source
    • Azure Resources Collected
    • Required Permissions
  • GCP Data Source
    • GCP Resources Collected
    • Required Permissions
    • Troubleshooting
  • Okta Data Source
  • Cloudflare Data Source
  • Integrations
    • Archer IRM Integration
    • Email Integration
    • Jira Integration
    • Slack Integration
    • ServiceNow Integration
    • Splunk Integration
    • Sumo Logic Integration
  • Authentication
  • API Documentation

Frameworks

  • Frameworks
  • Viewing Framework Compliance
  • Creating Frameworks
  • Modifying Frameworks
  • Deleting Frameworks

Reporting

  • Scheduled Reports
  • Export Data

Workflows

  • Workflows Overview
  • Create Workflows

Data Explorer

  • Overview
  • Tables
  • Views
  • Running Queries
  • A.I. Assistant

Policies

  • Creating Policies
  • Modifying Policies
  • Policy Exceptions
  • Managing Policy Coverage

PUSH API

  • Overview
  • Authentication
  • Custom Client Development
  • Generic Client
Powered by 

Authentication

The Push API uses mutual TLS to authenticate both the client and server and to encrypt the data in transit between the client and server.

Secberus manages a certificate authority for the purpose of managing certificates for use with the Push API system.

Updated 20 days ago


Overview
Custom Client Development