RFC 9411: Benchmarking Methodology for Network Security Device Performance
In plain English — editorial summary, not part of the RFC
This document provides benchmarking terminology and methodology for next-generation network security devices, including next-generation firewalls (NGFWs) and next-generation intrusion prevention systems (NGIPSs). The main areas covered in this document are test terminology, test configuration parameters, and benchmarking methodology for NGFWs and NGIPSs. (It is assumed that readers have a working knowledge of these devices and the security functionality they contain.) This document aims to improve the applicability, reproducibility, and transparency of benchmarks and to align the test methodology with today's increasingly complex layer 7 security-centric network application use cases. As a result, this document makes RFC 3511 obsolete.
Document record
- Document ID
- RFC9411
- Published
- March 2023
- Authors
- B. Balarajah; C. Rossenhoevel; B. Monkman
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 51
- Also known as
- —
- Obsoletes:
- RFC 3511
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9693Benchmarking Methodology for Stateful NATxy GatewaysCurrent
January 2025
- RFC 6985IMIX Genome: Specification of Variable Packet Sizes for Additional TestingCurrent
July 2013
- RFC 6076Basic Telephony SIP End-to-End Performance MetricsCurrent
January 2011
- RFC 4814Hash and Stuffing: Overlooked Factors in Network Device BenchmarkingCurrent
March 2007
- RFC 9408A YANG Network Data Model for Service Attachment Points (SAPs)Current
June 2023
- RFC 9417Service Assurance for Intent-Based Networking ArchitectureCurrent
July 2023
- RFC 9418A YANG Data Model for Service AssuranceCurrent
July 2023
- RFC 9424Indicators of Compromise (IoCs) and Their Role in Attack DefenceCurrent
August 2023
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?