Skip to main content
As a Security Administrator, your primary responsibilities in Snapsec include managing organization structure, user identity, access controls, scan policies, and enterprise compliance SLAs.

​
1. Configure Single Sign-On (SSO) & MFA

  1. Navigate to Platform > Administration > SSO & Authentication.
  2. Select your Identity Provider (Okta, Microsoft Entra ID / Azure AD, Google Workspace, PingFederate).
  3. Upload your IdP SAML Metadata XML or enter the OIDC Client ID and Secret.
  4. Enforce Multi-Factor Authentication (MFA) and define session timeout thresholds.

​
2. Define Departments, Teams, and Roles

Snapsec provides granular Role-Based Access Control (RBAC):
  • Super Administrator: Full system configuration, licenses, and security policies.
  • Security Administrator: Workspace governance, scan scheduling, and user management.
  • Security Analyst: Finding triage, blocker review, and reporting.
  • Developer / Engineer: Scoped read/write access to assigned projects and assets.
  • Auditor / Executive: Read-only reporting and SLA analytics.
Map your identity provider groups to Snapsec teams under Platform > Administration > Users & Teams.

​
3. Set Remediation SLA Policies

Establish binding remediation timelines based on vulnerability severity:
  • Critical: 7 calendar days
  • High: 14 calendar days
  • Medium: 30 calendar days
  • Low: 90 calendar days
Configure automated notifications to trigger at 50% and 80% SLA thresholds to prevent breach violations.

​
4. Connect Enterprise Ticketing (Jira / ServiceNow)

  1. Navigate to Integrations & Automation > Ticketing Integrations.
  2. Authenticate your Jira Cloud or Jira Server instance.
  3. Map Snapsec fields (Title, Severity, Steps to Reproduce, Remediation Advice) to your development teams’ Jira issue types.