808bits

Barracuda KTINA FIPS Crypto Module

FIPS 140-2 certificate #2874 · Barracuda Networks · data as of 2026-10-21

Barracuda KTINA FIPS Crypto Module, from Barracuda Networks, holds FIPS 140-2 certificate #2874 at overall level 1. The validation is historical: agencies may keep the module in existing systems but not buy it new. Below are its validation history, algorithm certificates and security policy, drawn from the NIST CMVP entry.

Historical. Moved to historical list due to dependency on certificate #2458. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated with the module "Barracuda Cryptographic Software Module" validated to FIPS 140-2 under Cert. #2458

Certificate

Certificate number2874
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorBarracuda Networks · website
Software versions7.1

Module description

Quoted from the NIST CMVP entry for this certificate.

The Barracuda KTINA FIPS Crypto Module is a Linux kernel module library that provides fundamental cryptographic functions for applications in Barracuda security products that require FIPS 140-2 approved cryptographic functions.

Security level exceptions

  • Roles, Services, and Authentication: Level 2
  • Physical Security: N/A
  • Design Assurance: Level 3

Approved algorithms (4)

AlgorithmCAVP certificates
AES4150
HMAC2720
SHS3416
Triple-DES2267

Tested configurations

  • Barracuda NextGen Firewall and Control Center OS 7 on Microsoft Windows 2012 (64-bit) Hyper-V running on a Dell PowerEdge R320 with PAA
  • Barracuda NextGen Firewall and Control Center OS 7 on Microsoft Windows 2012 (64-bit) Hyper-V running on a Dell PowerEdge R320 without PAA (single-user mode)

Validation history

DateTypeLab
2017-04-05InitialBOOZ ALLEN HAMILTON

Status timeline

As observed by this tracker's snapshots. NIST publishes no dates for list moves; observation began 2026-08-21, so earlier changes carry no date.

  • 2026-08-21: first observed by this tracker, status historical
  • Validation dates on record: 2017-04-05

Source documents