> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usenabla.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Generate FIPS cryptographic assessment from ZIP bundle

> Upload a ZIP archive containing multiple evidence sources (SBOMs, Terraform state, Kubernetes manifests, Ansible playbooks, package locks, system info) and generate FIPS 140-2/140-3 cryptographic compliance assessment. Detects cryptographic libraries, validates FIPS compliance, and checks for weak algorithms.



## OpenAPI

````yaml api-reference/openapi.json post /v1/fips
openapi: 3.1.0
info:
  title: Nabla Evidence Engine API
  version: 1.0.0
  description: >-
    Compliance evidence orchestration and security analysis API. Analyze
    firmware binaries, infrastructure-as-code, and cloud configurations for
    FedRAMP, CMMC, FIPS, and other compliance frameworks.
  contact:
    name: Nabla
    url: https://www.usenabla.com
servers:
  - url: https://api.usenabla.com
    description: Production
  - url: https://api.gov.usenabla.com
    description: GovCloud
  - url: http://localhost:8080
    description: Local Development
security:
  - CustomerKey: []
tags:
  - name: Evidence
    description: Compliance evidence generation and analysis
  - name: Firmware
    description: Binary firmware security analysis
  - name: FIPS
    description: FIPS 140-2/140-3 cryptographic compliance
paths:
  /v1/fips:
    post:
      tags:
        - FIPS
      summary: Generate FIPS cryptographic assessment from ZIP bundle
      description: >-
        Upload a ZIP archive containing multiple evidence sources (SBOMs,
        Terraform state, Kubernetes manifests, Ansible playbooks, package locks,
        system info) and generate FIPS 140-2/140-3 cryptographic compliance
        assessment. Detects cryptographic libraries, validates FIPS compliance,
        and checks for weak algorithms.
      operationId: generateFipsAssessment
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - name
                - format
                - zip_content
              properties:
                name:
                  type: string
                  description: Name for the FIPS assessment
                  example: production-crypto-audit
                format:
                  type: string
                  enum:
                    - oscal
                    - yaml
                    - json
                  description: Output format for the assessment
                  example: json
                zip_content:
                  type: string
                  description: >-
                    Base64-encoded ZIP archive. Supported file types:
                    sbom.json/spdx.json (SBOM), *.tfstate (Terraform),
                    *.yaml/manifest.yaml (Kubernetes), playbook.yaml (Ansible),
                    package-lock.json/Cargo.lock/go.mod/poetry.lock (package
                    managers), system_info.json/openssl.json (system crypto
                    info)
                  example: UEsDBBQAAAAIAA==
      responses:
        '200':
          $ref: '#/components/responses/EvidenceResponse'
        '400':
          $ref: '#/components/responses/BadRequest'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '422':
          $ref: '#/components/responses/Unprocessable'
      security:
        - CustomerKey: []
components:
  responses:
    EvidenceResponse:
      description: Evidence assessment completed successfully
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/EvidenceResponse'
    BadRequest:
      description: Bad request - invalid input
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    Unauthorized:
      description: Unauthorized - invalid or missing API key
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    Unprocessable:
      description: Unprocessable entity - unable to parse evidence
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
  schemas:
    EvidenceResponse:
      type: object
      required:
        - id
        - status
        - created_at
        - assessment
        - artifacts
      properties:
        id:
          type: string
          format: uuid
          description: Unique identifier for this assessment
        status:
          type: string
          enum:
            - completed
            - failed
          description: Assessment status
        created_at:
          type: string
          format: date-time
          description: Timestamp when assessment was created
        assessment:
          $ref: '#/components/schemas/ComplianceAssessment'
        artifacts:
          type: array
          items:
            $ref: '#/components/schemas/Artifact'
          description: Generated artifacts (assessment files, diagrams)
    Error:
      type: object
      required:
        - error
        - message
      properties:
        error:
          type: string
          description: Error type
        message:
          type: string
          description: Error message
        code:
          type: string
          description: HTTP status code
        requestId:
          type: string
          description: Request identifier for debugging
    ComplianceAssessment:
      type: object
      required:
        - id
        - framework
        - version
        - timestamp
        - controls
        - summary
      properties:
        id:
          type: string
          format: uuid
        framework:
          type: string
          description: Compliance framework name
          enum:
            - NIST 800-53
            - NIST 800-171
            - NIST 800-172
            - CMMC
            - FIPS 140-2
            - FIPS 140-3
            - NIST SP 800-193
          example: NIST 800-53
        version:
          type: string
          description: Framework version
          example: Rev. 5
        timestamp:
          type: string
          format: date-time
        controls:
          type: array
          items:
            $ref: '#/components/schemas/ControlAssessment'
        summary:
          $ref: '#/components/schemas/AssessmentSummary'
    Artifact:
      type: object
      required:
        - filename
        - content_type
        - content_base64
        - size_bytes
      properties:
        filename:
          type: string
          description: Artifact filename
          example: nist80053-assessment.json
        content_type:
          type: string
          description: MIME type
          example: application/json
        content_base64:
          type: string
          description: Base64-encoded artifact content
        size_bytes:
          type: integer
          description: Size in bytes
        diagram:
          type: string
          description: Mermaid diagram content (if applicable)
    ControlAssessment:
      type: object
      required:
        - control_id
        - title
        - status
        - findings
        - evidence
      properties:
        control_id:
          type: string
          description: Control identifier
          example: SC-13
        title:
          type: string
          description: Control title
          example: Cryptographic Protection
        status:
          type: string
          enum:
            - satisfied
            - not-satisfied
            - not-applicable
          description: Control satisfaction status
        findings:
          type: array
          items:
            type: string
          description: List of findings or issues
        evidence:
          type: array
          items:
            type: string
          description: Evidence supporting the assessment
    AssessmentSummary:
      type: object
      required:
        - total_controls
        - satisfied
        - not_satisfied
        - not_applicable
      properties:
        total_controls:
          type: integer
          description: Total number of controls assessed
        satisfied:
          type: integer
          description: Number of satisfied controls
        not_satisfied:
          type: integer
          description: Number of not-satisfied controls
        not_applicable:
          type: integer
          description: Number of not-applicable controls
  securitySchemes:
    CustomerKey:
      type: apiKey
      in: header
      name: X-Customer-Key
      description: Customer API key for authentication

````