idnits 2.17.1 draft-ietf-bmwg-ngfw-performance-09.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 1 instance of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. == There are 1 instance of lines with non-RFC3849-compliant IPv6 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document date (May 21, 2021) is 1069 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Obsolete informational reference (is this intentional?): RFC 2616 (Obsoleted by RFC 7230, RFC 7231, RFC 7232, RFC 7233, RFC 7234, RFC 7235) -- Obsolete informational reference (is this intentional?): RFC 3511 (Obsoleted by RFC 9411) Summary: 0 errors (**), 0 flaws (~~), 4 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Benchmarking Methodology Working Group B. Balarajah 3 Internet-Draft 4 Intended status: Informational C. Rossenhoevel 5 Expires: November 22, 2021 EANTC AG 6 B. Monkman 7 NetSecOPEN 8 May 21, 2021 10 Benchmarking Methodology for Network Security Device Performance 11 draft-ietf-bmwg-ngfw-performance-09 13 Abstract 15 This document provides benchmarking terminology and methodology for 16 next-generation network security devices including next-generation 17 firewalls (NGFW), next-generation intrusion detection and prevention 18 systems (NGIDS/NGIPS) and unified threat management (UTM) 19 implementations. This document aims to strongly improve the 20 applicability, reproducibility, and transparency of benchmarks and to 21 align the test methodology with today's increasingly complex layer 7 22 security centric network application use cases. The main areas 23 covered in this document are test terminology, test configuration 24 parameters, and benchmarking methodology for NGFW and NGIDS/NGIPS to 25 start with. 27 Status of This Memo 29 This Internet-Draft is submitted in full conformance with the 30 provisions of BCP 78 and BCP 79. 32 Internet-Drafts are working documents of the Internet Engineering 33 Task Force (IETF). Note that other groups may also distribute 34 working documents as Internet-Drafts. The list of current Internet- 35 Drafts is at https://datatracker.ietf.org/drafts/current/. 37 Internet-Drafts are draft documents valid for a maximum of six months 38 and may be updated, replaced, or obsoleted by other documents at any 39 time. It is inappropriate to use Internet-Drafts as reference 40 material or to cite them other than as "work in progress." 42 This Internet-Draft will expire on November 22, 2021. 44 Copyright Notice 46 Copyright (c) 2021 IETF Trust and the persons identified as the 47 document authors. All rights reserved. 49 This document is subject to BCP 78 and the IETF Trust's Legal 50 Provisions Relating to IETF Documents 51 (https://trustee.ietf.org/license-info) in effect on the date of 52 publication of this document. Please review these documents 53 carefully, as they describe your rights and restrictions with respect 54 to this document. Code Components extracted from this document must 55 include Simplified BSD License text as described in Section 4.e of 56 the Trust Legal Provisions and are provided without warranty as 57 described in the Simplified BSD License. 59 Table of Contents 61 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 62 2. Requirements . . . . . . . . . . . . . . . . . . . . . . . . 4 63 3. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 64 4. Test Setup . . . . . . . . . . . . . . . . . . . . . . . . . 4 65 4.1. Test Bed Configuration . . . . . . . . . . . . . . . . . 4 66 4.2. DUT/SUT Configuration . . . . . . . . . . . . . . . . . . 6 67 4.2.1. Security Effectiveness Configuration . . . . . . . . 12 68 4.3. Test Equipment Configuration . . . . . . . . . . . . . . 12 69 4.3.1. Client Configuration . . . . . . . . . . . . . . . . 12 70 4.3.2. Backend Server Configuration . . . . . . . . . . . . 15 71 4.3.3. Traffic Flow Definition . . . . . . . . . . . . . . . 17 72 4.3.4. Traffic Load Profile . . . . . . . . . . . . . . . . 17 73 5. Test Bed Considerations . . . . . . . . . . . . . . . . . . . 18 74 6. Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . 19 75 6.1. Introduction . . . . . . . . . . . . . . . . . . . . . . 19 76 6.2. Detailed Test Results . . . . . . . . . . . . . . . . . . 21 77 6.3. Benchmarks and Key Performance Indicators . . . . . . . . 21 78 7. Benchmarking Tests . . . . . . . . . . . . . . . . . . . . . 22 79 7.1. Throughput Performance with Application Traffic Mix . . . 23 80 7.1.1. Objective . . . . . . . . . . . . . . . . . . . . . . 23 81 7.1.2. Test Setup . . . . . . . . . . . . . . . . . . . . . 23 82 7.1.3. Test Parameters . . . . . . . . . . . . . . . . . . . 23 83 7.1.4. Test Procedures and Expected Results . . . . . . . . 25 84 7.2. TCP/HTTP Connections Per Second . . . . . . . . . . . . . 26 85 7.2.1. Objective . . . . . . . . . . . . . . . . . . . . . . 26 86 7.2.2. Test Setup . . . . . . . . . . . . . . . . . . . . . 26 87 7.2.3. Test Parameters . . . . . . . . . . . . . . . . . . . 26 88 7.2.4. Test Procedures and Expected Results . . . . . . . . 27 89 7.3. HTTP Throughput . . . . . . . . . . . . . . . . . . . . . 29 90 7.3.1. Objective . . . . . . . . . . . . . . . . . . . . . . 29 91 7.3.2. Test Setup . . . . . . . . . . . . . . . . . . . . . 29 92 7.3.3. Test Parameters . . . . . . . . . . . . . . . . . . . 29 93 7.3.4. Test Procedures and Expected Results . . . . . . . . 31 94 7.4. HTTP Transaction Latency . . . . . . . . . . . . . . . . 32 95 7.4.1. Objective . . . . . . . . . . . . . . . . . . . . . . 32 96 7.4.2. Test Setup . . . . . . . . . . . . . . . . . . . . . 32 97 7.4.3. Test Parameters . . . . . . . . . . . . . . . . . . . 32 98 7.4.4. Test Procedures and Expected Results . . . . . . . . 34 99 7.5. Concurrent TCP/HTTP Connection Capacity . . . . . . . . . 35 100 7.5.1. Objective . . . . . . . . . . . . . . . . . . . . . . 35 101 7.5.2. Test Setup . . . . . . . . . . . . . . . . . . . . . 35 102 7.5.3. Test Parameters . . . . . . . . . . . . . . . . . . . 35 103 7.5.4. Test Procedures and Expected Results . . . . . . . . 37 104 7.6. TCP/HTTPS Connections per Second . . . . . . . . . . . . 38 105 7.6.1. Objective . . . . . . . . . . . . . . . . . . . . . . 38 106 7.6.2. Test Setup . . . . . . . . . . . . . . . . . . . . . 38 107 7.6.3. Test Parameters . . . . . . . . . . . . . . . . . . . 38 108 7.6.4. Test Procedures and Expected Results . . . . . . . . 40 109 7.7. HTTPS Throughput . . . . . . . . . . . . . . . . . . . . 41 110 7.7.1. Objective . . . . . . . . . . . . . . . . . . . . . . 41 111 7.7.2. Test Setup . . . . . . . . . . . . . . . . . . . . . 41 112 7.7.3. Test Parameters . . . . . . . . . . . . . . . . . . . 42 113 7.7.4. Test Procedures and Expected Results . . . . . . . . 43 114 7.8. HTTPS Transaction Latency . . . . . . . . . . . . . . . . 44 115 7.8.1. Objective . . . . . . . . . . . . . . . . . . . . . . 44 116 7.8.2. Test Setup . . . . . . . . . . . . . . . . . . . . . 44 117 7.8.3. Test Parameters . . . . . . . . . . . . . . . . . . . 44 118 7.8.4. Test Procedures and Expected Results . . . . . . . . 46 119 7.9. Concurrent TCP/HTTPS Connection Capacity . . . . . . . . 47 120 7.9.1. Objective . . . . . . . . . . . . . . . . . . . . . . 47 121 7.9.2. Test Setup . . . . . . . . . . . . . . . . . . . . . 47 122 7.9.3. Test Parameters . . . . . . . . . . . . . . . . . . . 47 123 7.9.4. Test Procedures and Expected Results . . . . . . . . 49 124 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 50 125 9. Security Considerations . . . . . . . . . . . . . . . . . . . 50 126 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 50 127 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 51 128 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 51 129 12.1. Normative References . . . . . . . . . . . . . . . . . . 51 130 12.2. Informative References . . . . . . . . . . . . . . . . . 51 131 Appendix A. Test Methodology - Security Effectiveness Evaluation 52 132 A.1. Test Objective . . . . . . . . . . . . . . . . . . . . . 52 133 A.2. Test Bed Setup . . . . . . . . . . . . . . . . . . . . . 52 134 A.3. Test Parameters . . . . . . . . . . . . . . . . . . . . . 53 135 A.3.1. DUT/SUT Configuration Parameters . . . . . . . . . . 53 136 A.3.2. Test Equipment Configuration Parameters . . . . . . . 53 137 A.4. Test Results Validation Criteria . . . . . . . . . . . . 53 138 A.5. Measurement . . . . . . . . . . . . . . . . . . . . . . . 54 139 A.6. Test Procedures and Expected Results . . . . . . . . . . 55 140 A.6.1. Step 1: Background Traffic . . . . . . . . . . . . . 55 141 A.6.2. Step 2: CVE Emulation . . . . . . . . . . . . . . . . 55 142 Appendix B. DUT/SUT Classification . . . . . . . . . . . . . . . 55 143 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 56 145 1. Introduction 147 15 years have passed since IETF recommended test methodology and 148 terminology for firewalls initially ([RFC3511]). The requirements 149 for network security element performance and effectiveness have 150 increased tremendously since then. Security function implementations 151 have evolved to more advanced areas and have diversified into 152 intrusion detection and prevention, threat management, analysis of 153 encrypted traffic, etc. In an industry of growing importance, well- 154 defined, and reproducible key performance indicators (KPIs) are 155 increasingly needed as they enable fair and reasonable comparison of 156 network security functions. All these reasons have led to the 157 creation of a new next-generation network security device 158 benchmarking document and this document obsoletes [RFC3511]. 160 2. Requirements 162 The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 163 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 164 "OPTIONAL" in this document are to be interpreted as described in BCP 165 14 [RFC2119], [RFC8174] when, and only when, they appear in all 166 capitals, as shown here. 168 3. Scope 170 This document provides testing terminology and testing methodology 171 for modern and next-generation network security devices. It covers 172 the validation of security effectiveness configurations of network 173 security devices, followed by performance benchmark testing. This 174 document focuses on advanced, realistic, and reproducible testing 175 methods. Additionally, it describes test bed environments, test tool 176 requirements, and test result formats. 178 4. Test Setup 180 Test setup defined in this document is applicable to all benchmarking 181 tests described in Section 7. The test setup MUST be contained 182 within an Isolated Test Environment (see Section 3 of [RFC6815]). 184 4.1. Test Bed Configuration 186 Test bed configuration MUST ensure that any performance implications 187 that are discovered during the benchmark testing aren't due to the 188 inherent physical network limitations such as the number of physical 189 links and forwarding performance capabilities (throughput and 190 latency) of the network devices in the test bed. For this reason, 191 this document recommends avoiding external devices such as switches 192 and routers in the test bed wherever possible. 194 In some deployment scenarios, the network security devices (Device 195 Under Test/System Under Test) are connected to routers and switches, 196 which will reduce the number of entries in MAC or ARP tables of the 197 Device Under Test/System Under Test (DUT/SUT). If MAC or ARP tables 198 have many entries, this may impact the actual DUT/SUT performance due 199 to MAC and ARP/ND (Neighbor Discovery) table lookup processes. This 200 document also recommends using test equipment with the capability of 201 emulating layer 3 routing functionality instead of adding external 202 routers in the test bed. 204 The test bed setup Option 1 (Figure 1) is the RECOMMENDED test bed 205 setup for the benchmarking test. 207 +-----------------------+ +-----------------------+ 208 | +-------------------+ | +-----------+ | +-------------------+ | 209 | | Emulated Router(s)| | | | | | Emulated Router(s)| | 210 | | (Optional) | +----- DUT/SUT +-----+ (Optional) | | 211 | +-------------------+ | | | | +-------------------+ | 212 | +-------------------+ | +-----------+ | +-------------------+ | 213 | | Clients | | | | Servers | | 214 | +-------------------+ | | +-------------------+ | 215 | | | | 216 | Test Equipment | | Test Equipment | 217 +-----------------------+ +-----------------------+ 219 Figure 1: Test Bed Setup - Option 1 221 If the test equipment used is not capable of emulating layer 3 222 routing functionality or if the numbers of used ports are mismatched 223 between test equipment and the DUT/SUT (need for a test equipment 224 ports aggregation), the test setup can be configured as shown in 225 Figure 2. 227 +-------------------+ +-----------+ +--------------------+ 228 |Aggregation Switch/| | | | Aggregation Switch/| 229 | Router +------+ DUT/SUT +------+ Router | 230 | | | | | | 231 +----------+--------+ +-----------+ +--------+-----------+ 232 | | 233 | | 234 +-----------+-----------+ +-----------+-----------+ 235 | | | | 236 | +-------------------+ | | +-------------------+ | 237 | | Emulated Router(s)| | | | Emulated Router(s)| | 238 | | (Optional) | | | | (Optional) | | 239 | +-------------------+ | | +-------------------+ | 240 | +-------------------+ | | +-------------------+ | 241 | | Clients | | | | Servers | | 242 | +-------------------+ | | +-------------------+ | 243 | | | | 244 | Test Equipment | | Test Equipment | 245 +-----------------------+ +-----------------------+ 247 Figure 2: Test Bed Setup - Option 2 249 4.2. DUT/SUT Configuration 251 A unique DUT/SUT configuration MUST be used for all benchmarking 252 tests described in Section 7. Since each DUT/SUT will have their own 253 unique configuration, users SHOULD configure their device with the 254 same parameters and security features that would be used in the 255 actual deployment of the device or a typical deployment in order to 256 achieve maximum network security coverage. 258 Table 1 and Table 2 below describe the RECOMMENDED and OPTIONAL sets 259 of network security feature list for NGFW and NGIDS/NGIPS 260 respectively. The selected security features SHOULD be consistently 261 enabled on the DUT/SUT for all the benchmarking tests described in 262 Section 7. 264 To improve repeatability, a summary of the DUT/SUT configuration 265 including a description of all enabled DUT/SUT features MUST be 266 published with the benchmarking results. 268 +------------------------+ 269 | NGFW | 270 +--------------- +-------------+----------+ 271 | | | | 272 |DUT/SUT Features| RECOMMENDED | OPTIONAL | 273 | | | | 274 +----------------+-------------+----------+ 275 |SSL Inspection | x | | 276 +----------------+-------------+----------+ 277 |IDS/IPS | x | | 278 +----------------+-------------+----------+ 279 |Anti-Spyware | x | | 280 +----------------+-------------+----------+ 281 |Anti-Virus | x | | 282 +----------------+-------------+----------+ 283 |Anti-Botnet | x | | 284 +----------------+-------------+----------+ 285 |Web Filtering | | x | 286 +----------------+-------------+----------+ 287 |Data Loss | | | 288 |Protection (DLP)| | x | 289 +----------------+-------------+----------+ 290 |DDoS | | x | 291 +----------------+-------------+----------+ 292 |Certificate | | x | 293 |Validation | | | 294 +----------------+-------------+----------+ 295 |Logging and | x | | 296 |Reporting | | | 297 +----------------+-------------+----------+ 298 |Application | x | | 299 |Identification | | | 300 +----------------+-------------+----------+ 302 Table 1: NGFW Security Features 303 +------------------------+ 304 | NGIDS/NGIPS | 305 +----------------+-------------+----------+ 306 | | | | 307 |DUT/SUT Features| RECOMMENDED | OPTIONAL | 308 | | | | 309 +----------------+-------------+----------+ 310 |SSL Inspection | x | | 311 +----------------+-------------+----------+ 312 |Anti-Malware | x | | 313 +----------------+-------------+----------+ 314 |Anti-Spyware | x | | 315 +----------------+-------------+----------+ 316 |Anti-Botnet | x | | 317 +----------------+-------------+----------+ 318 |Logging and | x | | 319 |Reporting | | | 320 +----------------+-------------+----------+ 321 |Application | x | | 322 |Identification | | | 323 +----------------+-------------+----------+ 324 |Deep Packet | x | | 325 |Inspection | | | 326 +----------------+-------------+----------+ 327 |Anti-Evasion | x | | 328 +----------------+-------------+----------+ 330 Table 2: NGIDS/NGIPS Security Features 332 The following table provides a brief description of the security 333 features. 335 +------------------+------------------------------------------------+ 336 | DUT/SUT Features | Description | 337 +------------------+------------------------------------------------+ 338 | SSL Inspection | DUT/SUT intercepts and decrypts inbound HTTPS | 339 | | traffic between servers and clients. Once the | 340 | | content inspection has been completed, DUT/SUT | 341 | | encrypts the HTTPS traffic with ciphers | 342 | | and keys used by the clients and servers. | 343 +------------------+------------------------------------------------+ 344 | IDS/IPS | DUT/SUT detects and blocks exploits | 345 | | targeting known and unknown vulnerabilities | 346 | | across the monitored network. | 347 +------------------+------------------------------------------------+ 348 | Anti-Malware | DUT/SUT detects and prevents the transmission | 349 | | of malicious executable code and any associated| 350 | | communications across the monitored network. | 351 | | This includes data exfiltration as well as | 352 | | command and control channels. | 353 +------------------+------------------------------------------------+ 354 | Anti-Spyware | Anti-Spyware is a subcategory of Anti Malware. | 355 | | Spyware transmits information without the | 356 | | user's knowledge or permission. DUT/SUT detects| 357 | | and block initial infection or transmission of | 358 | | data. | 359 +------------------+------------------------------------------------+ 360 | Anti-Botnet | DUT/SUT detects traffic to or from botnets. | 361 +------------------+------------------------------------------------+ 362 | Anti-Evasion | DUT/SUT detects and mitigates attacks that have| 363 | | been obfuscated in some manner. | 364 +------------------+------------------------------------------------+ 365 | Web Filtering | DUT/SUT detects and blocks malicious website | 366 | | including defined classifications of website | 367 | | across the monitored network. | 368 +------------------+------------------------------------------------+ 369 | DLP | DUT/SUT detects and prevents data breaches and | 370 | | data exfiltration, or it detects and blocks the| 371 | | transmission of sensitive data across the | 372 | | monitored network. | 373 +------------------+------------------------------------------------+ 374 | Certificate | DUT/SUT validates certificates used in | 375 | Validation | encrypted communications across the monitored | 376 | | network. | 377 +------------------+------------------------------------------------+ 378 | Logging and | DUT/SUT logs and reports all traffic at the | 379 | Reporting | flow level across the monitored network. | 380 +------------------+------------------------------------------------+ 381 | Application | DUT/SUT detects known applications as defined | 382 | Identification | within the traffic mix selected across | 383 | | the monitored network. | 384 +------------------+------------------------------------------------+ 386 Table 3: Security Feature Description 388 In summary, a DUT/SUT SHOULD be configured as follows: 390 o All RECOMMENDED security inspections enabled 392 o Disposition of all flows of traffic are logged - Logging to an 393 external device is permissible 395 o Geographical location filtering and Application Identification and 396 Control configured to be triggered based on a site or application 397 from the defined traffic mix 399 In addition, a realistic number of access control rules (ACL) SHOULD 400 be configured on the DUT/SUT where ACL's are configurable and also 401 reasonable based on the deployment scenario. This document 402 determines the number of access policy rules for four different 403 classes of DUT/SUT; namely Extra Small (XS), Small (S), Medium (M) 404 and Large (L). A sample DUT/SUT classification is described in 405 Appendix B. 407 The Access Control Rules (ACL) defined in Table 4 MUST be configured 408 from top to bottom in the correct order as shown in the table. This 409 is due to ACL types listed in specificity decreasing order, with 410 "block" first, followed by "allow", representing typical ACL based 411 security policy. The ACL entries SHOULD be configured with routable 412 IP subnets by the DUT/SUT. (Note: There will be differences between 413 how security vendors implement ACL decision making.) The configured 414 ACL MUST NOT block the security and measurement traffic used for the 415 benchmarking tests. 417 +---------------+ 418 | DUT/SUT | 419 | Classification| 420 | # Rules | 421 +-----------+-----------+--------------------+------+---+---+---+---+ 422 | | Match | | | | | | | 423 | Rules Type| Criteria | Description |Action| XS| S | M | L | 424 +-------------------------------------------------------------------+ 425 |Application|Application| Any application | block| 5 | 10| 20| 50| 426 |layer | | not included in | | | | | | 427 | | | the measurement | | | | | | 428 | | | traffic | | | | | | 429 +-------------------------------------------------------------------+ 430 |Transport |Src IP and | Any src IP subnet | block| 25| 50|100|250| 431 |layer |TCP/UDP | used and any dst | | | | | | 432 | |Dst ports | ports not used in | | | | | | 433 | | | the measurement | | | | | | 434 | | | traffic | | | | | | 435 +-------------------------------------------------------------------+ 436 |IP layer |Src/Dst IP | Any src/dst IP | block| 25| 50|100|250| 437 | | | subnet not used | | | | | | 438 | | | in the measurement | | | | | | 439 | | | traffic | | | | | | 440 +-------------------------------------------------------------------+ 441 |Application|Application| Half of the | allow| 10| 10| 10| 10| 442 |layer | | applications | | | | | | 443 | | | included in the | | | | | | 444 | | | measurement traffic| | | | | | 445 | | |(see the note below)| | | | | | 446 +-------------------------------------------------------------------+ 447 |Transport |Src IP and | Half of the src | allow| >1| >1| >1| >1| 448 |layer |TCP/UDP | IP used and any | | | | | | 449 | |Dst ports | dst ports used in | | | | | | 450 | | | the measurement | | | | | | 451 | | | traffic | | | | | | 452 | | | (one rule per | | | | | | 453 | | | subnet) | | | | | | 454 +-------------------------------------------------------------------+ 455 |IP layer |Src IP | The rest of the | allow| >1| >1| >1| >1| 456 | | | src IP subnet | | | | | | 457 | | | range used in the | | | | | | 458 | | | measurement | | | | | | 459 | | | traffic | | | | | | 460 | | | (one rule per | | | | | | 461 | | | subnet) | | | | | | 462 +-----------+-----------+--------------------+------+---+---+---+---+ 464 Table 4: DUT/SUT Access List 466 Note: If the half of applications included in the measurement traffic 467 is less than 10, the missing number of ACL entries (dummy rules) can 468 be configured for any application traffic not included in the 469 measurement traffic. 471 4.2.1. Security Effectiveness Configuration 473 The Security features (defined in table 1 and 2) of the DUT/SUT MUST 474 be configured effectively in such a way to detect, prevent, and 475 report the defined security Vulnerability sets. This Section defines 476 the selection of the security Vulnerability sets from Common 477 Vulnerabilities and Exposures (CVE) list for the testing. The 478 vulnerability set SHOULD reflect a minimum of 500 CVEs from no older 479 than 10 calendar years to the current year. These CVEs SHOULD be 480 selected with a focus on in-use software commonly found in business 481 applications, with a Common Vulnerability Scoring System (CVSS) 482 Severity of High (7-10). 484 This document is primarily focused on performance benchmarking. 485 However, it is RECOMMENDED to validate the security features 486 configuration of the DUT/SUT by evaluating the security effectiveness 487 as a prerequisite for performance benchmarking tests defined in the 488 section 7. In case the Benchmarking tests are performed without 489 evaluating security effectiveness, the test report MUST explain the 490 implications of this. The methodology for evaluating Security 491 effectiveness is defined in Appendix A. 493 4.3. Test Equipment Configuration 495 In general, test equipment allows configuring parameters in different 496 protocol layers. These parameters thereby influence the traffic 497 flows which will be offered and impact performance measurements. 499 This section specifies common test equipment configuration parameters 500 applicable for all benchmarking tests defined in Section 7. Any 501 benchmarking test specific parameters are described under the test 502 setup section of each benchmarking test individually. 504 4.3.1. Client Configuration 506 This section specifies which parameters SHOULD be considered while 507 configuring clients using test equipment. Also, this section 508 specifies the RECOMMENDED values for certain parameters. 510 4.3.1.1. TCP Stack Attributes 512 The TCP stack SHOULD use a congestion control algorithm at client and 513 server endpoints. The default IPv4 and IPv6 MSS segments size SHOULD 514 be set to 1460 bytes and 1440 bytes respectively and a TX and RX 515 initial receive windows of 64 KByte. Client initial congestion 516 window SHOULD NOT exceed 10 times the MSS. Delayed ACKs are 517 permitted and the maximum client delayed ACK SHOULD NOT exceed 10 518 times the MSS before a forced ACK. Up to three retries SHOULD be 519 allowed before a timeout event is declared. All traffic MUST set the 520 TCP PSH flag to high. The source port range SHOULD be in the range 521 of 1024 - 65535. Internal timeout SHOULD be dynamically scalable per 522 RFC 793. The client SHOULD initiate and close TCP connections. The 523 TCP connection MUST be initiated via a TCP three way handshake (SYN, 524 SYN/ACK, ACK), and it MUST be closed via either a TCP three way close 525 (FIN, FIN/ACK, ACK), or a TCP four way close (FIN, ACK, FIN, ACK). 527 4.3.1.2. Client IP Address Space 529 The sum of the client IP space SHOULD contain the following 530 attributes. 532 o The IP blocks SHOULD consist of multiple unique, discontinuous 533 static address blocks. 535 o A default gateway is permitted. 537 o The DSCP (differentiated services code point) marking is set to DF 538 (Default Forwarding) '000000' on IPv4 Type of Service (ToS) field 539 and IPv6 traffic class field. 541 The following equation can be used to define the total number of 542 client IP addresses that will be configured on the test equipment. 544 Desired total number of client IP = Target throughput [Mbit/s] / 545 Average throughput per IP address [Mbit/s] 547 As shown in the example list below, the value for "Average throughput 548 per IP address" can be varied depending on the deployment and use 549 case scenario. 551 (Option 1) DUT/SUT deployment scenario 1 : 6-7 Mbit/s per IP (e.g. 552 1,400-1,700 IPs per 10Gbit/s throughput) 554 (Option 2) DUT/SUT deployment scenario 2 : 0.1-0.2 Mbit/s per IP 555 (e.g. 50,000-100,000 IPs per 10Gbit/s throughput) 557 Based on deployment and use case scenario, client IP addresses SHOULD 558 be distributed between IPv4 and IPv6 type. The Following options can 559 be considered for a selection of traffic mix ratio. 561 (Option 1) 100 % IPv4, no IPv6 563 (Option 2) 80 % IPv4, 20% IPv6 565 (Option 3) 50 % IPv4, 50% IPv6 567 (Option 4) 20 % IPv4, 80% IPv6 569 (Option 5) no IPv4, 100% IPv6 571 Note: The IANA has assigned IP address range for the testing purpose 572 as described in Section 8. If the test scenario requires additional 573 number of IP addresses or subnets than the IANA assigned, this 574 document recommends to use non routable Private IPv4 address ranges 575 or Unique Local Address (ULA) IPv6 address ranges for the testing. 577 4.3.1.3. Emulated Web Browser Attributes 579 The emulated web client contains attributes that will materially 580 affect how traffic is loaded. The objective is to emulate modern, 581 typical browser attributes to improve realism of the result set. 583 For HTTP traffic emulation, the emulated browser MUST negotiate HTTP 584 version 1.1 or higher. Depending on test scenarios and chosen HTTP 585 version, the browser MAY open multiple TCP connections per Server 586 endpoint IP at any time depending on how many sequential transactions 587 need to be processed. For HTTP/2 or HTTP/3, the browser MAY open 588 Multiple concurrent streams per connection (multiplexing). If HTTP/3 589 is used the browser MUST open Quick UDP Internet Connections (QUIC) 590 connection. HTTP settings such as number of connection per server 591 IP, number of requests per connection and number of streams per 592 connection MUST be documented. This document refers to [RFC8446] for 593 HTTP/2. The browser SHOULD advertise a User-Agent header. The 594 browser SHOULD enforce content length validation. Depending on test 595 scenarios and selected HTTP version, HTTP header compression MAY be 596 set to enable or disable. This setting (compression enabled or 597 disabled) MUST be documented in the report. 599 For encrypted traffic, the following attributes SHALL define the 600 negotiated encryption parameters. The test clients MUST use TLS 601 version 1.2 or higher. TLS record size MAY be optimized for the 602 HTTPS response object size up to a record size of 16 KByte. If 603 Server Name Indication (SNI) is required in the traffic mix profile, 604 the client endpoint MUST send TLS Extension Server Name Indication 605 (SNI) information when opening a security tunnel. Each client 606 connection MUST perform a full handshake with server certificate and 607 MUST NOT use session reuse or resumption. 609 The following TLS 1.2 supported ciphers and keys are RECOMMENDED to 610 use for HTTPS based benchmarking tests defined in Section 7. 612 1. ECHDE-ECDSA-AES128-GCM-SHA256 with Prime256v1 (Signature Hash 613 Algorithm: ecdsa_secp256r1_sha256 and Supported group: sepc256r1) 615 2. ECDHE-RSA-AES128-GCM-SHA256 with RSA 2048 (Signature Hash 616 Algorithm: rsa_pkcs1_sha256 and Supported group: sepc256) 618 3. ECDHE-ECDSA-AES256-GCM-SHA384 with Secp521 (Signature Hash 619 Algorithm: ecdsa_secp384r1_sha384 and Supported group: sepc521r1) 621 4. ECDHE-RSA-AES256-GCM-SHA384 with RSA 4096 (Signature Hash 622 Algorithm: rsa_pkcs1_sha384 and Supported group: secp256) 624 Note: The above ciphers and keys were those commonly used enterprise 625 grade encryption cipher suites for TLS 1.2. It is recognized that 626 these will evolve over time. Individual certification bodies SHOULD 627 use ciphers and keys that reflect evolving use cases. These choices 628 MUST be documented in the resulting test reports with detailed 629 information on the ciphers and keys used along with reasons for the 630 choices. 632 [RFC8446] defines the following cipher suites for use with TLS 1.3. 634 1. TLS_AES_128_GCM_SHA256 636 2. TLS_AES_256_GCM_SHA384 638 3. TLS_CHACHA20_POLY1305_SHA256 640 4. TLS_AES_128_CCM_SHA256 642 5. TLS_AES_128_CCM_8_SHA256 644 4.3.2. Backend Server Configuration 646 This section specifies which parameters should be considered while 647 configuring emulated backend servers using test equipment. 649 4.3.2.1. TCP Stack Attributes 651 The TCP stack on the server side SHOULD be configured similar to the 652 client side configuration described in Section 4.3.1.1. In addition, 653 server initial congestion window MUST NOT exceed 10 times the MSS. 654 Delayed ACKs are permitted and the maximum server delayed ACK MUST 655 NOT exceed 10 times the MSS before a forced ACK. 657 4.3.2.2. Server Endpoint IP Addressing 659 The sum of the server IP space SHOULD contain the following 660 attributes. 662 o The server IP blocks SHOULD consist of unique, discontinuous 663 static address blocks with one IP per Server Fully Qualified 664 Domain Name (FQDN) endpoint per test port. 666 o A default gateway is permitted. The DSCP (differentiated services 667 code point) marking is set to DF (Default Forwarding) '000000' on 668 IPv4 Type of Service (ToS) field and IPv6 traffic class field. 670 o The server IP addresses SHOULD be distributed between IPv4 and 671 IPv6 with a ratio identical to the clients distribution ratio. 673 Note: The IANA has assigned IP address range for the testing purpose 674 as described in Section 8. If the test scenario requires additional 675 number of IP addresses or subnets than the IANA assigned, this 676 document recommends to use non routable Private IPv4 address ranges 677 or Unique Local Address (ULA) IPv6 address ranges for the testing. 679 4.3.2.3. HTTP / HTTPS Server Pool Endpoint Attributes 681 The server pool for HTTP SHOULD listen on TCP port 80 and emulate the 682 same HTTP version and settings chosen by the client (emulated web 683 browser). The Server MUST advertise server type in the Server 684 response header [RFC2616]. For HTTPS server, TLS 1.2 or higher MUST 685 be used with a maximum record size of 16 KByte and MUST NOT use 686 ticket resumption or Session ID reuse. The server SHOULD listen on 687 port TCP 443. The server SHALL serve a certificate to the client. 688 The HTTPS server MUST check Host SNI information with the FQDN if the 689 SNI is in use. Cipher suite and key size on the server side MUST be 690 configured similar to the client side configuration described in 691 Section 4.3.1.3. 693 4.3.3. Traffic Flow Definition 695 This section describes the traffic pattern between client and server 696 endpoints. At the beginning of the test, the server endpoint 697 initializes and will be ready to accept connection states including 698 initialization of the TCP stack as well as bound HTTP and HTTPS 699 servers. When a client endpoint is needed, it will initialize and be 700 given attributes such as a MAC and IP address. The behavior of the 701 client is to sweep through the given server IP space, generating a 702 recognizable service by the DUT. Sequential and pseudorandom sweep 703 methods are acceptable. The method used MUST be stated in the final 704 report. Thus, a balanced, mesh between client endpoints and server 705 endpoints will be generated in a client IP and port server IP and 706 port combination. Each client endpoint performs the same actions as 707 other endpoints, with the difference being the source IP of the 708 client endpoint and the target server IP pool. The client MUST use 709 the server's IP address or Fully Qualified Domain Names (FQDN) in 710 Host Headers [RFC2616]. 712 4.3.3.1. Description of Intra-Client Behavior 714 Client endpoints are independent of other clients that are 715 concurrently executing. When a client endpoint initiates traffic, 716 this section describes how the client steps through different 717 services. Once the test is initialized, the client endpoints 718 randomly hold (perform no operation) for a few milliseconds to allow 719 for better randomization of the start of client traffic. Each client 720 will either open a new TCP connection or connect to a TCP persistence 721 stack still open to that specific server. At any point that the 722 traffic profile may require encryption, a TLS encryption tunnel will 723 form presenting the URL or IP address request to the server. If 724 using SNI, the server MUST then perform an SNI name check with the 725 proposed FQDN compared to the domain embedded in the certificate. 726 Only when correct, will the server process the HTTPS response object. 727 The initial response object to the server is based on benchmarking 728 tests described in Section 7. Multiple additional sub-URLs (response 729 objects on the service page) MAY be requested simultaneously. This 730 MAY be to the same server IP as the initial URL. Each sub-object 731 will also use a conical FQDN and URL path, as observed in the traffic 732 mix used. 734 4.3.4. Traffic Load Profile 736 The loading of traffic is described in this section. The loading of 737 a traffic load profile has five distinct phases: Init, ramp up, 738 sustain, ramp down, and collection. 740 1. During the Init phase, test bed devices including the client and 741 server endpoints should negotiate layer 2-3 connectivity such as 742 MAC learning and ARP. Only after successful MAC learning or ARP/ 743 ND resolution SHALL the test iteration move to the next phase. 744 No measurements are made in this phase. The minimum RECOMMEND 745 time for Init phase is 5 seconds. During this phase, the 746 emulated clients SHOULD NOT initiate any sessions with the DUT/ 747 SUT, in contrast, the emulated servers should be ready to accept 748 requests from DUT/SUT or from emulated clients. 750 2. In the ramp up phase, the test equipment SHOULD start to generate 751 the test traffic. It SHOULD use a set of approximate number of 752 unique client IP addresses actively to generate traffic. The 753 traffic SHOULD ramp up from zero to desired target objective. 754 The target objective will be defined for each benchmarking test. 755 The duration for the ramp up phase MUST be configured long 756 enough, so that the test equipment does not overwhelm the DUT/ 757 SUT's stated performance metrics defined in Section 6.3 namely; 758 TCP Connections Per Second, Inspected Throughput, Concurrent TCP 759 Connections, and Application Transactions Per Second. No 760 measurements are made in this phase. 762 3. Sustain phase starts when all required clients are active and 763 operating at their desired load condition. In the sustain phase, 764 the test equipment SHOULD continue generating traffic to constant 765 target value for a constant number of active clients. The 766 minimum RECOMMENDED time duration for sustain phase is 300 767 seconds. This is the phase where measurements occur. The test 768 equipment SHOULD measure and record statistics continuously. The 769 sampling interval for collecting the row results and calculating 770 the statistics SHOULD be less than 2 seconds. 772 4. In the ramp down/close phase, no new connections are established, 773 and no measurements are made. The time duration for ramp up and 774 ramp down phase SHOULD be the same. 776 5. The last phase is administrative and will occur when the test 777 equipment merges and collates the report data. 779 5. Test Bed Considerations 781 This section recommends steps to control the test environment and 782 test equipment, specifically focusing on virtualized environments and 783 virtualized test equipment. 785 1. Ensure that any ancillary switching or routing functions between 786 the system under test and the test equipment do not limit the 787 performance of the traffic generator. This is specifically 788 important for virtualized components (vSwitches, vRouters). 790 2. Verify that the performance of the test equipment matches and 791 reasonably exceeds the expected maximum performance of the DUT/ 792 SUT. 794 3. Assert that the test bed characteristics are stable during the 795 entire test session. Several factors might influence stability 796 specifically, for virtualized test beds. For example, additional 797 workloads in a virtualized system, load balancing, and movement 798 of virtual machines during the test, or simple issues such as 799 additional heat created by high workloads leading to an emergency 800 CPU performance reduction. 802 Test bed preparation may be performed either by configuring the DUT 803 in the most trivial setup (fast forwarding) or without presence of 804 the DUT. 806 6. Reporting 808 This section describes how the final report should be formatted and 809 presented. The final test report MAY have two major sections; 810 Introduction and detailed test results sections. 812 6.1. Introduction 814 The following attributes SHOULD be present in the introduction 815 section of the test report. 817 1. The time and date of the execution of the test MUST be prominent. 819 2. Summary of test bed software and hardware details 821 A. DUT/SUT hardware/virtual configuration 823 + This section SHOULD clearly identify the make and model of 824 the DUT/SUT 826 + The port interfaces, including speed and link information 827 MUST be documented. 829 + If the DUT/SUT is a Virtual Network Function (VNF), host 830 (server) hardware and software details, interface 831 acceleration type such as DPDK and SR-IOV used CPU cores, 832 used RAM, and the resource sharing (e.g. Pinning details 833 and NUMA Node) configuration MUST be documented. The 834 virtual components such as Hypervisor, virtual switch 835 version MUST be also documented. 837 + Any additional hardware relevant to the DUT/SUT such as 838 controllers MUST be documented 840 B. DUT/SUT software 842 + The operating system name MUST be documented 844 + The version MUST be documented 846 + The specific configuration MUST be documented 848 C. DUT/SUT enabled features 850 + Configured DUT/SUT features (see Table 1 and Table 2) MUST 851 be documented 853 + Attributes of those featured MUST be documented 855 + Any additional relevant information about features MUST be 856 documented 858 D. Test equipment hardware and software 860 + Test equipment vendor name 862 + Hardware details including model number, interface type 864 + Test equipment firmware and test application software 865 version 867 E. Key test parameters 869 + Used cipher suites and keys 871 + IPv4 and IPv6 traffic distribution 873 + Number of configured ACL 875 F. Details of application traffic mix used in the benchmarking 876 test "Throughput Performance with Application Traffic Mix" 877 (Section 7.1) 879 + Name of applications and layer 7 protocols 880 + Percentage of emulated traffic for each application and 881 layer 7 protocols 883 + Percentage of encrypted traffic and used cipher suites and 884 keys (The RECOMMENDED ciphers and keys are defined in 885 Section 4.3.1.3) 887 + Used object sizes for each application and layer 7 888 protocols 890 3. Results Summary / Executive Summary 892 A. Results SHOULD resemble a pyramid in how it is reported, with 893 the introduction section documenting the summary of results 894 in a prominent, easy to read block. 896 6.2. Detailed Test Results 898 In the result section of the test report, the following attributes 899 SHOULD be present for each benchmarking test. 901 a. KPIs MUST be documented separately for each benchmarking test. 902 The format of the KPI metrics SHOULD be presented as described in 903 Section 6.3. 905 b. The next level of details SHOULD be graphs showing each of these 906 metrics over the duration (sustain phase) of the test. This 907 allows the user to see the measured performance stability changes 908 over time. 910 6.3. Benchmarks and Key Performance Indicators 912 This section lists key performance indicators (KPIs) for overall 913 benchmarking tests. All KPIs MUST be measured during the sustain 914 phase of the traffic load profile described in Section 4.3.4. All 915 KPIs MUST be measured from the result output of test equipment. 917 o Concurrent TCP Connections 918 The aggregate number of simultaneous connections between hosts 919 across the DUT/SUT, or between hosts and the DUT/SUT (defined in 920 [RFC2647]). 922 o TCP Connections Per Second 923 The average number of successfully established TCP connections per 924 second between hosts across the DUT/SUT, or between hosts and the 925 DUT/SUT. The TCP connection must be initiated via a TCP three way 926 handshake (SYN, SYN/ACK, ACK). Then the TCP session data is sent. 927 The TCP session MUST be closed via either a TCP three way close 928 (FIN, FIN/ACK, ACK), or a TCP four way close (FIN, ACK, FIN, ACK), 929 and not by a RST. 931 o Application Transactions Per Second 932 The average number of successfully completed transactions per 933 second. For a particular transaction to be considered successful, 934 all data must have been transferred in its entirety. In case of 935 HTTP(S) transaction, it must have a valid status code, and the 936 appropriate FIN, FIN/ACK sequence must have been completed. 938 o TLS Handshake Rate 939 The average number of successfully established TLS connections per 940 second between hosts across the DUT/SUT, or between hosts and the 941 DUT/SUT. 943 o Inspected Throughput 944 The number of bits per second of examined and allowed traffic a 945 network security device is able to transmit to the correct 946 destination interface(s) in response to a specified offered load. 947 The throughput benchmarking tests defined in Section 7 SHOULD 948 measure the average Layer 2 throughput value when the DUT/SUT is 949 "inspecting" traffic. This document recommends presenting the 950 inspected throughput value in Gbit/s rounded to two places of 951 precision with a more specific Kbit/s in parenthesis. 953 o Time to First Byte (TTFB) 954 TTFB is the elapsed time between the start of sending the TCP SYN 955 packet from the client and the client receiving the first packet 956 of application data from the server or DUT/SUT. The benchmarking 957 tests HTTP Transaction Latency (Section 7.4) and HTTPS Transaction 958 Latency (Section 7.8) measure the minimum, average and maximum 959 TTFB. The value SHOULD be expressed in millisecond. 961 o URL Response time / Time to Last Byte (TTLB) 962 URL Response time / TTLB is the elapsed time between the start of 963 sending the TCP SYN packet from the client and the client 964 receiving the last packet of application data from the server or 965 DUT/SUT. The benchmarking tests HTTP Transaction Latency 966 (Section 7.4) and HTTPS Transaction Latency (Section 7.8) measure 967 the minimum, average and maximum TTLB. The value SHOULD be 968 expressed in millisecond. 970 7. Benchmarking Tests 971 7.1. Throughput Performance with Application Traffic Mix 973 7.1.1. Objective 975 Using a relevant application traffic mix, determine the sustainable 976 inspected throughput supported by the DUT/SUT. 978 Based on customer use case, users can choose the application traffic 979 mix for this test. The details about the traffic mix MUST be 980 documented in the report. At least the following traffic mix details 981 MUST be documented and reported together with the test results: 983 Name of applications and layer 7 protocols 985 Percentage of emulated traffic for each application and layer 7 986 protocols 988 Percentage of encrypted traffic and used cipher suites and keys 989 (The RECOMMENDED ciphers and keys are defined in Section 4.3.1.3.) 991 Used object sizes for each application and layer 7 protocols 993 7.1.2. Test Setup 995 Test bed setup MUST be configured as defined in Section 4. Any 996 benchmarking test specific test bed configuration changes MUST be 997 documented. 999 7.1.3. Test Parameters 1001 In this section, the benchmarking test specific parameters SHOULD be 1002 defined. 1004 7.1.3.1. DUT/SUT Configuration Parameters 1006 DUT/SUT parameters MUST conform to the requirements defined in 1007 Section 4.2. Any configuration changes for this specific 1008 benchmarking test MUST be documented. In case the DUT is configured 1009 without SSL inspection feature, the test report MUST explain the 1010 implications of this to the relevant application traffic mix 1011 encrypted traffic. 1013 7.1.3.2. Test Equipment Configuration Parameters 1015 Test equipment configuration parameters MUST conform to the 1016 requirements defined in Section 4.3. Following parameters MUST be 1017 noted for this benchmarking test: 1019 Client IP address range defined in Section 4.3.1.2 1021 Server IP address range defined in Section 4.3.2.2 1023 Traffic distribution ratio between IPv4 and IPv6 defined in 1024 Section 4.3.1.2 1026 Target inspected throughput: Aggregated line rate of interface(s) 1027 used in the DUT/SUT or the value defined based on requirement for 1028 a specific deployment scenario 1030 Initial inspected throughput: 10% of the "Target inspected 1031 throughput" 1033 One of the ciphers and keys defined in Section 4.3.1.3 are 1034 RECOMMENDED to use for this benchmarking test. 1036 7.1.3.3. Traffic Profile 1038 Traffic profile: This test MUST be run with a relevant application 1039 traffic mix profile. 1041 7.1.3.4. Test Results Validation Criteria 1043 The following test Criteria is defined as test results validation 1044 criteria. Test results validation criteria MUST be monitored during 1045 the whole sustain phase of the traffic load profile. 1047 a. Number of failed application transactions (receiving any HTTP 1048 response code other than 200 OK) MUST be less than 0.001% (1 out 1049 of 100,000 transactions) of total attempt transactions. 1051 b. Number of Terminated TCP connections due to unexpected TCP RST 1052 sent by DUT/SUT MUST be less than 0.001% (1 out of 100,000 1053 connections) of total initiated TCP connections. 1055 7.1.3.5. Measurement 1057 Following KPI metrics MUST be reported for this benchmarking test: 1059 Mandatory KPIs (benchmarks): Inspected Throughput, TTFB (minimum, 1060 average, and maximum), TTLB (minimum, average, and maximum) and 1061 Application Transactions Per Second 1063 Note: TTLB MUST be reported along with the object size used in the 1064 traffic profile. 1066 Optional KPIs: TCP Connections Per Second and TLS Handshake Rate 1068 7.1.4. Test Procedures and Expected Results 1070 The test procedures are designed to measure the inspected throughput 1071 performance of the DUT/SUT at the sustaining period of traffic load 1072 profile. The test procedure consists of three major steps. This 1073 test procedure MAY be repeated multiple times with different IP 1074 types; IPv4 only, IPv6 only and IPv4 and IPv6 mixed traffic 1075 distribution. 1077 7.1.4.1. Step 1: Test Initialization and Qualification 1079 Verify the link status of all connected physical interfaces. All 1080 interfaces are expected to be in "UP" status. 1082 Configure traffic load profile of the test equipment to generate test 1083 traffic at the "Initial inspected throughput" rate as described in 1084 the parameters Section 7.1.3.2. The test equipment SHOULD follow the 1085 traffic load profile definition as described in Section 4.3.4. The 1086 DUT/SUT SHOULD reach the "Initial inspected throughput" during the 1087 sustain phase. Measure all KPI as defined in Section 7.1.3.5. The 1088 measured KPIs during the sustain phase MUST meet all the test results 1089 validation criteria defined in Section 7.1.3.4. 1091 If the KPI metrics do not meet the test results validation criteria, 1092 the test procedure MUST NOT be continued to step 2. 1094 7.1.4.2. Step 2: Test Run with Target Objective 1096 Configure test equipment to generate traffic at the "Target inspected 1097 throughput" rate defined in the parameter table. The test equipment 1098 SHOULD follow the traffic load profile definition as described in 1099 Section 4.3.4. The test equipment SHOULD start to measure and record 1100 all specified KPIs. Continue the test until all traffic profile 1101 phases are completed. 1103 Within the test results validation criteria, the DUT/SUT is expected 1104 to reach the desired value of the target objective ("Target inspected 1105 throughput") in the sustain phase. Follow step 3, if the measured 1106 value does not meet the target value or does not fulfill the test 1107 results validation criteria. 1109 7.1.4.3. Step 3: Test Iteration 1111 Determine the achievable average inspected throughput within the test 1112 results validation criteria. Final test iteration MUST be performed 1113 for the test duration defined in Section 4.3.4. 1115 7.2. TCP/HTTP Connections Per Second 1117 7.2.1. Objective 1119 Using HTTP traffic, determine the sustainable TCP connection 1120 establishment rate supported by the DUT/SUT under different 1121 throughput load conditions. 1123 To measure connections per second, test iterations MUST use the 1124 different fixed HTTP response object sizes (the different load 1125 conditions) defined in Section 7.2.3.2. 1127 7.2.2. Test Setup 1129 Test bed setup SHOULD be configured as defined in Section 4. Any 1130 specific test bed configuration changes such as number of interfaces 1131 and interface type, etc. MUST be documented. 1133 7.2.3. Test Parameters 1135 In this section, benchmarking test specific parameters SHOULD be 1136 defined. 1138 7.2.3.1. DUT/SUT Configuration Parameters 1140 DUT/SUT parameters MUST conform to the requirements defined in 1141 Section 4.2. Any configuration changes for this specific 1142 benchmarking test MUST be documented. 1144 7.2.3.2. Test Equipment Configuration Parameters 1146 Test equipment configuration parameters MUST conform to the 1147 requirements defined in Section 4.3. Following parameters MUST be 1148 documented for this benchmarking test: 1150 Client IP address range defined in Section 4.3.1.2 1152 Server IP address range defined in Section 4.3.2.2 1154 Traffic distribution ratio between IPv4 and IPv6 defined in 1155 Section 4.3.1.2 1157 Target connections per second: Initial value from product datasheet 1158 or the value defined based on requirement for a specific deployment 1159 scenario 1161 Initial connections per second: 10% of "Target connections per 1162 second" (an optional parameter for documentation) 1163 The client SHOULD negotiate HTTP and close the connection with FIN 1164 immediately after completion of one transaction. In each test 1165 iteration, client MUST send GET command requesting a fixed HTTP 1166 response object size. 1168 The RECOMMENDED response object sizes are 1, 2, 4, 16, and 64 KByte. 1170 7.2.3.3. Test Results Validation Criteria 1172 The following test Criteria is defined as test results validation 1173 criteria. Test results validation criteria MUST be monitored during 1174 the whole sustain phase of the traffic load profile. 1176 a. Number of failed Application transactions (receiving any HTTP 1177 response code other than 200 OK) MUST be less than 0.001% (1 out 1178 of 100,000 transactions) of total attempt transactions. 1180 b. Number of Terminated TCP connections due to unexpected TCP RST 1181 sent by DUT/SUT MUST be less than 0.001% (1 out of 100,000 1182 connections) of total initiated TCP connections. 1184 c. During the sustain phase, traffic SHOULD be forwarded at a 1185 constant rate (considered as a constant rate if any deviation of 1186 traffic forwarding rate is less than 5%). 1188 d. Concurrent TCP connections MUST be constant during steady state 1189 and any deviation of concurrent TCP connections SHOULD be less 1190 than 10%. This confirms the DUT opens and closes TCP connections 1191 almost at the same rate. 1193 7.2.3.4. Measurement 1195 TCP Connections Per Second MUST be reported for each test iteration 1196 (for each object size). 1198 7.2.4. Test Procedures and Expected Results 1200 The test procedure is designed to measure the TCP connections per 1201 second rate of the DUT/SUT at the sustaining period of the traffic 1202 load profile. The test procedure consists of three major steps. 1203 This test procedure MAY be repeated multiple times with different IP 1204 types; IPv4 only, IPv6 only and IPv4 and IPv6 mixed traffic 1205 distribution. 1207 7.2.4.1. Step 1: Test Initialization and Qualification 1209 Verify the link status of all connected physical interfaces. All 1210 interfaces are expected to be in "UP" status. 1212 Configure the traffic load profile of the test equipment to establish 1213 "Initial connections per second" as defined in the parameters 1214 Section 7.2.3.2. The traffic load profile SHOULD be defined as 1215 described in Section 4.3.4. 1217 The DUT/SUT SHOULD reach the "Initial connections per second" before 1218 the sustain phase. The measured KPIs during the sustain phase MUST 1219 meet all the test results validation criteria defined in 1220 Section 7.2.3.3. 1222 If the KPI metrics do not meet the test results validation criteria, 1223 the test procedure MUST NOT be continued to "Step 2". 1225 7.2.4.2. Step 2: Test Run with Target Objective 1227 Configure test equipment to establish the target objective ("Target 1228 connections per second") defined in the parameters table. The test 1229 equipment SHOULD follow the traffic load profile definition as 1230 described in Section 4.3.4. 1232 During the ramp up and sustain phase of each test iteration, other 1233 KPIs such as inspected throughput, concurrent TCP connections and 1234 application transactions per second MUST NOT reach to the maximum 1235 value the DUT/SUT can support. The test results for specific test 1236 iterations SHOULD NOT be reported, if the above mentioned KPI 1237 (especially inspected throughput) reaches the maximum value. 1238 (Example: If the test iteration with 64 KByte of HTTP response object 1239 size reached the maximum inspected throughput limitation of the DUT, 1240 the test iteration MAY be interrupted and the result for 64 KByte 1241 SHOULD NOT be reported). 1243 The test equipment SHOULD start to measure and record all specified 1244 KPIs. Continue the test until all traffic profile phases are 1245 completed. 1247 Within the test results validation criteria, the DUT/SUT is expected 1248 to reach the desired value of the target objective ("Target 1249 connections per second") in the sustain phase. Follow step 3, if the 1250 measured value does not meet the target value or does not fulfill the 1251 test results validation criteria. 1253 7.2.4.3. Step 3: Test Iteration 1255 Determine the achievable TCP connections per second within the test 1256 results validation criteria. 1258 7.3. HTTP Throughput 1260 7.3.1. Objective 1262 Determine the sustainable inspected throughput of the DUT/SUT for 1263 HTTP transactions varying the HTTP response object size. 1265 7.3.2. Test Setup 1267 Test bed setup SHOULD be configured as defined in Section 4. Any 1268 specific test bed configuration changes such as number of interfaces 1269 and interface type, etc. must be documented. 1271 7.3.3. Test Parameters 1273 In this section, benchmarking test specific parameters SHOULD be 1274 defined. 1276 7.3.3.1. DUT/SUT Configuration Parameters 1278 DUT/SUT parameters MUST conform to the requirements defined in 1279 Section 4.2. Any configuration changes for this specific 1280 benchmarking test MUST be documented. 1282 7.3.3.2. Test Equipment Configuration Parameters 1284 Test equipment configuration parameters MUST conform to the 1285 requirements defined in Section 4.3. Following parameters MUST be 1286 documented for this benchmarking test: 1288 Client IP address range defined in Section 4.3.1.2 1290 Server IP address range defined in Section 4.3.2.2 1292 Traffic distribution ratio between IPv4 and IPv6 defined in 1293 Section 4.3.1.2 1295 Target inspected throughput: Aggregated line rate of interface(s) 1296 used in the DUT/SUT or the value defined based on requirement for a 1297 specific deployment scenario 1299 Initial inspected throughput: 10% of "Target inspected throughput" 1300 (an optional parameter for documentation) 1301 Number of HTTP response object requests (transactions) per 1302 connection: 10 1304 RECOMMENDED HTTP response object size: 1, 16, 64, 256 KByte, and 1305 mixed objects defined in the table 1307 +---------------------+---------------------+ 1308 | Object size (KByte) | Number of requests/ | 1309 | | Weight | 1310 +---------------------+---------------------+ 1311 | 0.2 | 1 | 1312 +---------------------+---------------------+ 1313 | 6 | 1 | 1314 +---------------------+---------------------+ 1315 | 8 | 1 | 1316 +---------------------+---------------------+ 1317 | 9 | 1 | 1318 +---------------------+---------------------+ 1319 | 10 | 1 | 1320 +---------------------+---------------------+ 1321 | 25 | 1 | 1322 +---------------------+---------------------+ 1323 | 26 | 1 | 1324 +---------------------+---------------------+ 1325 | 35 | 1 | 1326 +---------------------+---------------------+ 1327 | 59 | 1 | 1328 +---------------------+---------------------+ 1329 | 347 | 1 | 1330 +---------------------+---------------------+ 1332 Table 5: Mixed Objects 1334 7.3.3.3. Test Results Validation Criteria 1336 The following test Criteria is defined as test results validation 1337 criteria. Test results validation criteria MUST be monitored during 1338 the whole sustain phase of the traffic load profile. 1340 a. Number of failed Application transactions (receiving any HTTP 1341 response code other than 200 OK) MUST be less than 0.001% (1 out 1342 of 100,000 transactions) of attempt transactions. 1344 b. Traffic SHOULD be forwarded at a constant rate (considered as a 1345 constant rate if any deviation of traffic forwarding rate is less 1346 than 5%). 1348 c. Concurrent TCP connections MUST be constant during steady state 1349 and any deviation of concurrent TCP connections SHOULD be less 1350 than 10%. This confirms the DUT opens and closes TCP connections 1351 almost at the same rate. 1353 7.3.3.4. Measurement 1355 Inspected Throughput and HTTP Transactions per Second MUST be 1356 reported for each object size. 1358 7.3.4. Test Procedures and Expected Results 1360 The test procedure is designed to measure HTTP throughput of the DUT/ 1361 SUT. The test procedure consists of three major steps. This test 1362 procedure MAY be repeated multiple times with different IPv4 and IPv6 1363 traffic distribution and HTTP response object sizes. 1365 7.3.4.1. Step 1: Test Initialization and Qualification 1367 Verify the link status of all connected physical interfaces. All 1368 interfaces are expected to be in "UP" status. 1370 Configure traffic load profile of the test equipment to establish 1371 "Initial inspected throughput" as defined in the parameters 1372 Section 7.3.3.2. 1374 The traffic load profile SHOULD be defined as described in 1375 Section 4.3.4. The DUT/SUT SHOULD reach the "Initial inspected 1376 throughput" during the sustain phase. Measure all KPI as defined in 1377 Section 7.3.3.4. 1379 The measured KPIs during the sustain phase MUST meet the test results 1380 validation criteria "a" defined in Section 7.3.3.3. The test results 1381 validation criteria "b" and "c" are OPTIONAL for step 1. 1383 If the KPI metrics do not meet the test results validation criteria, 1384 the test procedure MUST NOT be continued to "Step 2". 1386 7.3.4.2. Step 2: Test Run with Target Objective 1388 Configure test equipment to establish the target objective ("Target 1389 inspected throughput") defined in the parameters table. The test 1390 equipment SHOULD start to measure and record all specified KPIs. 1391 Continue the test until all traffic profile phases are completed. 1393 Within the test results validation criteria, the DUT/SUT is expected 1394 to reach the desired value of the target objective in the sustain 1395 phase. Follow step 3, if the measured value does not meet the target 1396 value or does not fulfill the test results validation criteria. 1398 7.3.4.3. Step 3: Test Iteration 1400 Determine the achievable inspected throughput within the test results 1401 validation criteria and measure the KPI metric Transactions per 1402 Second. Final test iteration MUST be performed for the test duration 1403 defined in Section 4.3.4. 1405 7.4. HTTP Transaction Latency 1407 7.4.1. Objective 1409 Using HTTP traffic, determine the HTTP transaction latency when DUT 1410 is running with sustainable HTTP transactions per second supported by 1411 the DUT/SUT under different HTTP response object sizes. 1413 Test iterations MUST be performed with different HTTP response object 1414 sizes in two different scenarios. One with a single transaction and 1415 the other with multiple transactions within a single TCP connection. 1416 For consistency both the single and multiple transaction test MUST be 1417 configured with the same HTTP version 1419 Scenario 1: The client MUST negotiate HTTP and close the connection 1420 with FIN immediately after completion of a single transaction (GET 1421 and RESPONSE). 1423 Scenario 2: The client MUST negotiate HTTP and close the connection 1424 FIN immediately after completion of 10 transactions (GET and 1425 RESPONSE) within a single TCP connection. 1427 7.4.2. Test Setup 1429 Test bed setup SHOULD be configured as defined in Section 4. Any 1430 specific test bed configuration changes such as number of interfaces 1431 and interface type, etc. MUST be documented. 1433 7.4.3. Test Parameters 1435 In this section, benchmarking test specific parameters SHOULD be 1436 defined. 1438 7.4.3.1. DUT/SUT Configuration Parameters 1440 DUT/SUT parameters MUST conform to the requirements defined in 1441 Section 4.2. Any configuration changes for this specific 1442 benchmarking test MUST be documented. 1444 7.4.3.2. Test Equipment Configuration Parameters 1446 Test equipment configuration parameters MUST conform to the 1447 requirements defined in Section 4.3. Following parameters MUST be 1448 documented for this benchmarking test: 1450 Client IP address range defined in Section 4.3.1.2 1452 Server IP address range defined in Section 4.3.2.2 1454 Traffic distribution ratio between IPv4 and IPv6 defined in 1455 Section 4.3.1.2 1457 Target objective for scenario 1: 50% of the connection per second 1458 measured in benchmarking test TCP/HTTP Connections Per Second 1459 (Section 7.2) 1461 Target objective for scenario 2: 50% of the inspected throughput 1462 measured in benchmarking test HTTP Throughput (Section 7.3) 1464 Initial objective for scenario 1: 10% of Target objective for 1465 scenario 1" (an optional parameter for documentation) 1467 Initial objective for scenario 2: 10% of "Target objective for 1468 scenario 2" (an optional parameter for documentation) 1470 HTTP transaction per TCP connection: test scenario 1 with single 1471 transaction and the second scenario with 10 transactions 1473 HTTP with GET command requesting a single object. The RECOMMENDED 1474 object sizes are 1, 16, and 64 KByte. For each test iteration, 1475 client MUST request a single HTTP response object size. 1477 7.4.3.3. Test Results Validation Criteria 1479 The following test Criteria is defined as test results validation 1480 criteria. Test results validation criteria MUST be monitored during 1481 the whole sustain phase of the traffic load profile. Ramp up and 1482 ramp down phase SHOULD NOT be considered. 1484 a. Number of failed Application transactions (receiving any HTTP 1485 response code other than 200 OK) MUST be less than 0.001% (1 out 1486 of 100,000 transactions) of attempt transactions. 1488 b. Number of Terminated TCP connections due to unexpected TCP RST 1489 sent by DUT/SUT MUST be less than 0.001% (1 out of 100,000 1490 connections) of total initiated TCP connections. 1492 c. During the sustain phase, traffic SHOULD be forwarded at a 1493 constant rate (considered as a constant rate if any deviation of 1494 traffic forwarding rate is less than 5%). 1496 d. Concurrent TCP connections MUST be constant during steady state 1497 and any deviation of concurrent TCP connections SHOULD be less 1498 than 10%. This confirms the DUT opens and closes TCP connections 1499 almost at the same rate. 1501 e. After ramp up the DUT MUST achieve the "Target objective" defined 1502 in the parameter Section 7.4.3.2 and remain in that state for the 1503 entire test duration (sustain phase). 1505 7.4.3.4. Measurement 1507 TTFB (minimum, average and maximum) and TTLB (minimum, average and 1508 maximum) MUST be reported for each object size. 1510 7.4.4. Test Procedures and Expected Results 1512 The test procedure is designed to measure TTFB or TTLB when the DUT/ 1513 SUT is operating close to 50% of its maximum achievable connections 1514 per second or inspected throughput. This test procedure MAY be 1515 repeated multiple times with different IP types (IPv4 only, IPv6 only 1516 and IPv4 and IPv6 mixed traffic distribution), HTTP response object 1517 sizes and single and multiple transactions per connection scenarios. 1519 7.4.4.1. Step 1: Test Initialization and Qualification 1521 Verify the link status of all connected physical interfaces. All 1522 interfaces are expected to be in "UP" status. 1524 Configure traffic load profile of the test equipment to establish 1525 "Initial objective" as defined in the parameters Section 7.4.3.2. 1526 The traffic load profile can be defined as described in 1527 Section 4.3.4. 1529 The DUT/SUT SHOULD reach the "Initial objective" before the sustain 1530 phase. The measured KPIs during the sustain phase MUST meet all the 1531 test results validation criteria defined in Section 7.4.3.3. 1533 If the KPI metrics do not meet the test results validation criteria, 1534 the test procedure MUST NOT be continued to "Step 2". 1536 7.4.4.2. Step 2: Test Run with Target Objective 1538 Configure test equipment to establish "Target objective" defined in 1539 the parameters table. The test equipment SHOULD follow the traffic 1540 load profile definition as described in Section 4.3.4. 1542 The test equipment SHOULD start to measure and record all specified 1543 KPIs. Continue the test until all traffic profile phases are 1544 completed. 1546 Within the test results validation criteria, the DUT/SUT MUST reach 1547 the desired value of the target objective in the sustain phase. 1549 Measure the minimum, average and maximum values of TFB and TTLB. 1551 7.5. Concurrent TCP/HTTP Connection Capacity 1553 7.5.1. Objective 1555 Determine the number of concurrent TCP connections that the DUT/ SUT 1556 sustains when using HTTP traffic. 1558 7.5.2. Test Setup 1560 Test bed setup SHOULD be configured as defined in Section 4. Any 1561 specific test bed configuration changes such as number of interfaces 1562 and interface type, etc. must be documented. 1564 7.5.3. Test Parameters 1566 In this section, benchmarking test specific parameters SHOULD be 1567 defined. 1569 7.5.3.1. DUT/SUT Configuration Parameters 1571 DUT/SUT parameters MUST conform to the requirements defined in 1572 Section 4.2. Any configuration changes for this specific 1573 benchmarking test MUST be documented. 1575 7.5.3.2. Test Equipment Configuration Parameters 1577 Test equipment configuration parameters MUST conform to the 1578 requirements defined in Section 4.3. Following parameters MUST be 1579 noted for this benchmarking test: 1581 Client IP address range defined in Section 4.3.1.2 1583 Server IP address range defined in Section 4.3.2.2 1584 Traffic distribution ratio between IPv4 and IPv6 defined in 1585 Section 4.3.1.2 1587 Target concurrent connection: Initial value from product datasheet 1588 or the value defined based on requirement for a specific 1589 deployment scenario. 1591 Initial concurrent connection: 10% of "Target concurrent 1592 connection" (an optional parameter for documentation) 1594 Maximum connections per second during ramp up phase: 50% of 1595 maximum connections per second measured in benchmarking test TCP/ 1596 HTTP Connections per second (Section 7.2) 1598 Ramp up time (in traffic load profile for "Target concurrent 1599 connection"): "Target concurrent connection" / "Maximum 1600 connections per second during ramp up phase" 1602 Ramp up time (in traffic load profile for "Initial concurrent 1603 connection"): "Initial concurrent connection" / "Maximum 1604 connections per second during ramp up phase" 1606 The client MUST negotiate HTTP and each client MAY open multiple 1607 concurrent TCP connections per server endpoint IP. 1609 Each client sends 10 GET commands requesting 1 KByte HTTP response 1610 object in the same TCP connection (10 transactions/TCP connection) 1611 and the delay (think time) between each transaction MUST be X 1612 seconds. 1614 X = ("Ramp up time" + "steady state time") /10 1616 The established connections SHOULD remain open until the ramp down 1617 phase of the test. During the ramp down phase, all connections 1618 SHOULD be successfully closed with FIN. 1620 7.5.3.3. Test Results Validation Criteria 1622 The following test Criteria is defined as test results validation 1623 criteria. Test results validation criteria MUST be monitored during 1624 the whole sustain phase of the traffic load profile. 1626 a. Number of failed Application transactions (receiving any HTTP 1627 response code other than 200 OK) MUST be less than 0.001% (1 out 1628 of 100,000 transaction) of total attempted transactions. 1630 b. Number of Terminated TCP connections due to unexpected TCP RST 1631 sent by DUT/SUT MUST be less than 0.001% (1 out of 100,000 1632 connections) of total initiated TCP connections. 1634 c. During the sustain phase, traffic SHOULD be forwarded at a 1635 constant rate (considered as a constant rate if any deviation of 1636 traffic forwarding rate is less than 5%). 1638 7.5.3.4. Measurement 1640 Average Concurrent TCP Connections MUST be reported for this 1641 benchmarking test. 1643 7.5.4. Test Procedures and Expected Results 1645 The test procedure is designed to measure the concurrent TCP 1646 connection capacity of the DUT/SUT at the sustaining period of 1647 traffic load profile. The test procedure consists of three major 1648 steps. This test procedure MAY be repeated multiple times with 1649 different IPv4 and IPv6 traffic distribution. 1651 7.5.4.1. Step 1: Test Initialization and Qualification 1653 Verify the link status of all connected physical interfaces. All 1654 interfaces are expected to be in "UP" status. 1656 Configure test equipment to establish "Initial concurrent TCP 1657 connections" defined in Section 7.5.3.2. Except ramp up time, the 1658 traffic load profile SHOULD be defined as described in Section 4.3.4. 1660 During the sustain phase, the DUT/SUT SHOULD reach the "Initial 1661 concurrent TCP connections". The measured KPIs during the sustain 1662 phase MUST meet all the test results validation criteria defined in 1663 Section 7.5.3.3. 1665 If the KPI metrics do not meet the test results validation criteria, 1666 the test procedure MUST NOT be continued to "Step 2". 1668 7.5.4.2. Step 2: Test Run with Target Objective 1670 Configure test equipment to establish the target objective ("Target 1671 concurrent TCP connections"). The test equipment SHOULD follow the 1672 traffic load profile definition (except ramp up time) as described in 1673 Section 4.3.4. 1675 During the ramp up and sustain phase, the other KPIs such as 1676 inspected throughput, TCP connections per second and application 1677 transactions per second MUST NOT reach to the maximum value that the 1678 DUT/SUT can support. 1680 The test equipment SHOULD start to measure and record KPIs defined in 1681 Section 7.5.3.4. Continue the test until all traffic profile phases 1682 are completed. 1684 Within the test results validation criteria, the DUT/SUT is expected 1685 to reach the desired value of the target objective in the sustain 1686 phase. Follow step 3, if the measured value does not meet the target 1687 value or does not fulfill the test results validation criteria. 1689 7.5.4.3. Step 3: Test Iteration 1691 Determine the achievable concurrent TCP connections capacity within 1692 the test results validation criteria. 1694 7.6. TCP/HTTPS Connections per Second 1696 7.6.1. Objective 1698 Using HTTPS traffic, determine the sustainable SSL/TLS session 1699 establishment rate supported by the DUT/SUT under different 1700 throughput load conditions. 1702 Test iterations MUST include common cipher suites and key strengths 1703 as well as forward looking stronger keys. Specific test iterations 1704 MUST include ciphers and keys defined in Section 7.6.3.2. 1706 For each cipher suite and key strengths, test iterations MUST use a 1707 single HTTPS response object size defined in the test equipment 1708 configuration parameters Section 7.6.3.2 to measure connections per 1709 second performance under a variety of DUT Security inspection load 1710 conditions. 1712 7.6.2. Test Setup 1714 Test bed setup SHOULD be configured as defined in Section 4. Any 1715 specific test bed configuration changes such as number of interfaces 1716 and interface type, etc. MUST be documented. 1718 7.6.3. Test Parameters 1720 In this section, benchmarking test specific parameters SHOULD be 1721 defined. 1723 7.6.3.1. DUT/SUT Configuration Parameters 1725 DUT/SUT parameters MUST conform to the requirements defined in 1726 Section 4.2. Any configuration changes for this specific 1727 benchmarking test MUST be documented. 1729 7.6.3.2. Test Equipment Configuration Parameters 1731 Test equipment configuration parameters MUST conform to the 1732 requirements defined in Section 4.3. Following parameters MUST be 1733 documented for this benchmarking test: 1735 Client IP address range defined in Section 4.3.1.2 1737 Server IP address range defined in Section 4.3.2.2 1739 Traffic distribution ratio between IPv4 and IPv6 defined in 1740 Section 4.3.1.2 1742 Target connections per second: Initial value from product datasheet 1743 or the value defined based on requirement for a specific deployment 1744 scenario. 1746 Initial connections per second: 10% of "Target connections per 1747 second" (an optional parameter for documentation) 1749 RECOMMENDED ciphers and keys defined in Section 4.3.1.3 1751 The client MUST negotiate HTTPS and close the connection with FIN 1752 immediately after completion of one transaction. In each test 1753 iteration, client MUST send GET command requesting a fixed HTTPS 1754 response object size. The RECOMMENDED object sizes are 1, 2, 4, 16, 1755 and 64 KByte. 1757 7.6.3.3. Test Results Validation Criteria 1759 The following test Criteria is defined as test results validation 1760 criteria: 1762 a. Number of failed Application transactions (receiving any HTTP 1763 response code other than 200 OK) MUST be less than 0.001% (1 out 1764 of 100,000 transactions) of attempt transactions. 1766 b. Number of Terminated TCP connections due to unexpected TCP RST 1767 sent by DUT/SUT MUST be less than 0.001% (1 out of 100,000 1768 connections) of total initiated TCP connections. 1770 c. During the sustain phase, traffic SHOULD be forwarded at a 1771 constant rate (considered as a constant rate if any deviation of 1772 traffic forwarding rate is less than 5%). 1774 d. Concurrent TCP connections MUST be constant during steady state 1775 and any deviation of concurrent TCP connections SHOULD be less 1776 than 10%. This confirms the DUT opens and closes TCP connections 1777 almost at the same rate. 1779 7.6.3.4. Measurement 1781 TCP Connections Per Second MUST be reported for each test iteration 1782 (for each object size). 1784 The KPI metric TLS Handshake Rate can be measured in the test using 1785 1KByte object size. 1787 7.6.4. Test Procedures and Expected Results 1789 The test procedure is designed to measure the TCP connections per 1790 second rate of the DUT/SUT at the sustaining period of traffic load 1791 profile. The test procedure consists of three major steps. This 1792 test procedure MAY be repeated multiple times with different IPv4 and 1793 IPv6 traffic distribution. 1795 7.6.4.1. Step 1: Test Initialization and Qualification 1797 Verify the link status of all connected physical interfaces. All 1798 interfaces are expected to be in "UP" status. 1800 Configure traffic load profile of the test equipment to establish 1801 "Initial connections per second" as defined in Section 7.6.3.2. The 1802 traffic load profile MAY be defined as described in Section 4.3.4. 1804 The DUT/SUT SHOULD reach the "Initial connections per second" before 1805 the sustain phase. The measured KPIs during the sustain phase MUST 1806 meet all the test results validation criteria defined in 1807 Section 7.6.3.3. 1809 If the KPI metrics do not meet the test results validation criteria, 1810 the test procedure MUST NOT be continued to "Step 2". 1812 7.6.4.2. Step 2: Test Run with Target Objective 1814 Configure test equipment to establish "Target connections per second" 1815 defined in the parameters table. The test equipment SHOULD follow 1816 the traffic load profile definition as described in Section 4.3.4. 1818 During the ramp up and sustain phase, other KPIs such as inspected 1819 throughput, concurrent TCP connections and application transactions 1820 per second MUST NOT reach the maximum value that the DUT/SUT can 1821 support. The test results for specific test iteration SHOULD NOT be 1822 reported, if the above mentioned KPI (especially inspected 1823 throughput) reaches the maximum value. (Example: If the test 1824 iteration with 64 KByte of HTTPS response object size reached the 1825 maximum inspected throughput limitation of the DUT, the test 1826 iteration MAY be interrupted and the result for 64 KByte SHOULD NOT 1827 be reported). 1829 The test equipment SHOULD start to measure and record all specified 1830 KPIs. Continue the test until all traffic profile phases are 1831 completed. 1833 Within the test results validation criteria, the DUT/SUT is expected 1834 to reach the desired value of the target objective ("Target 1835 connections per second") in the sustain phase. Follow step 3, if the 1836 measured value does not meet the target value or does not fulfill the 1837 test results validation criteria. 1839 7.6.4.3. Step 3: Test Iteration 1841 Determine the achievable connections per second within the test 1842 results validation criteria. 1844 7.7. HTTPS Throughput 1846 7.7.1. Objective 1848 Determine the sustainable inspected throughput of the DUT/SUT for 1849 HTTPS transactions varying the HTTPS response object size. 1851 Test iterations MUST include common cipher suites and key strengths 1852 as well as forward looking stronger keys. Specific test iterations 1853 MUST include the ciphers and keys defined in the parameter 1854 Section 7.7.3.2. 1856 7.7.2. Test Setup 1858 Test bed setup SHOULD be configured as defined in Section 4. Any 1859 specific test bed configuration changes such as number of interfaces 1860 and interface type, etc. must be documented. 1862 7.7.3. Test Parameters 1864 In this section, benchmarking test specific parameters SHOULD be 1865 defined. 1867 7.7.3.1. DUT/SUT Configuration Parameters 1869 DUT/SUT parameters MUST conform to the requirements defined in 1870 Section 4.2. Any configuration changes for this specific 1871 benchmarking test MUST be documented. 1873 7.7.3.2. Test Equipment Configuration Parameters 1875 Test equipment configuration parameters MUST conform to the 1876 requirements defined in Section 4.3. Following parameters MUST be 1877 documented for this benchmarking test: 1879 Client IP address range defined in Section 4.3.1.2 1881 Server IP address range defined in Section 4.3.2.2 1883 Traffic distribution ratio between IPv4 and IPv6 defined in 1884 Section 4.3.1.2 1886 Target inspected throughput: Aggregated line rate of interface(s) 1887 used in the DUT/SUT or the value defined based on requirement for a 1888 specific deployment scenario. 1890 Initial inspected throughput: 10% of "Target inspected throughput" 1891 (an optional parameter for documentation) 1893 Number of HTTPS response object requests (transactions) per 1894 connection: 10 1896 RECOMMENDED ciphers and keys defined in Section 4.3.1.3 1898 RECOMMENDED HTTPS response object size: 1, 16, 64, 256 KByte, and 1899 mixed objects defined in the Table 5 under the Section 7.3.3.2. 1901 7.7.3.3. Test Results Validation Criteria 1903 The following test Criteria is defined as test results validation 1904 criteria. Test results validation criteria MUST be monitored during 1905 the whole sustain phase of the traffic load profile. 1907 a. Number of failed Application transactions (receiving any HTTP 1908 response code other than 200 OK) MUST be less than 0.001% (1 out 1909 of 100,000 transactions) of attempt transactions. 1911 b. Traffic SHOULD be forwarded at a constant rate (considered as a 1912 constant rate if any deviation of traffic forwarding rate is less 1913 than 5%). 1915 c. Concurrent TCP connections MUST be constant during steady state 1916 and any deviation of concurrent TCP connections SHOULD be less 1917 than 10%. This confirms the DUT opens and closes TCP connections 1918 almost at the same rate. 1920 7.7.3.4. Measurement 1922 Inspected Throughput and HTTP Transactions per Second MUST be 1923 reported for each object size. 1925 7.7.4. Test Procedures and Expected Results 1927 The test procedure consists of three major steps. This test 1928 procedure MAY be repeated multiple times with different IPv4 and IPv6 1929 traffic distribution and HTTPS response object sizes. 1931 7.7.4.1. Step 1: Test Initialization and Qualification 1933 Verify the link status of all connected physical interfaces. All 1934 interfaces are expected to be in "UP" status. 1936 Configure traffic load profile of the test equipment to establish 1937 "Initial inspected throughput" as defined in the parameters 1938 Section 7.7.3.2. 1940 The traffic load profile SHOULD be defined as described in 1941 Section 4.3.4. The DUT/SUT SHOULD reach the "Initial inspected 1942 throughput" during the sustain phase. Measure all KPI as defined in 1943 Section 7.7.3.4. 1945 The measured KPIs during the sustain phase MUST meet the test results 1946 validation criteria "a" defined in Section 7.7.3.3. The test results 1947 validation criteria "b" and "c" are OPTIONAL for step 1. 1949 If the KPI metrics do not meet the test results validation criteria, 1950 the test procedure MUST NOT be continued to "Step 2". 1952 7.7.4.2. Step 2: Test Run with Target Objective 1954 Configure test equipment to establish the target objective ("Target 1955 inspected throughput") defined in the parameters table. The test 1956 equipment SHOULD start to measure and record all specified KPIs. 1957 Continue the test until all traffic profile phases are completed. 1959 Within the test results validation criteria, the DUT/SUT is expected 1960 to reach the desired value of the target objective in the sustain 1961 phase. Follow step 3, if the measured value does not meet the target 1962 value or does not fulfill the test results validation criteria. 1964 7.7.4.3. Step 3: Test Iteration 1966 Determine the achievable average inspected throughput within the test 1967 results validation criteria. Final test iteration MUST be performed 1968 for the test duration defined in Section 4.3.4. 1970 7.8. HTTPS Transaction Latency 1972 7.8.1. Objective 1974 Using HTTPS traffic, determine the HTTPS transaction latency when DUT 1975 is running with sustainable HTTPS transactions per second supported 1976 by the DUT/SUT under different HTTPS response object size. 1978 Scenario 1: The client MUST negotiate HTTPS and close the connection 1979 with FIN immediately after completion of a single transaction (GET 1980 and RESPONSE). 1982 Scenario 2: The client MUST negotiate HTTPS and close the connection 1983 with FIN immediately after completion of 10 transactions (GET and 1984 RESPONSE) within a single TCP connection. 1986 7.8.2. Test Setup 1988 Test bed setup SHOULD be configured as defined in Section 4. Any 1989 specific test bed configuration changes such as number of interfaces 1990 and interface type, etc. MUST be documented. 1992 7.8.3. Test Parameters 1994 In this section, benchmarking test specific parameters SHOULD be 1995 defined. 1997 7.8.3.1. DUT/SUT Configuration Parameters 1999 DUT/SUT parameters MUST conform to the requirements defined in 2000 Section 4.2. Any configuration changes for this specific 2001 benchmarking test MUST be documented. 2003 7.8.3.2. Test Equipment Configuration Parameters 2005 Test equipment configuration parameters MUST conform to the 2006 requirements defined in Section 4.3. Following parameters MUST be 2007 documented for this benchmarking test: 2009 Client IP address range defined in Section 4.3.1.2 2011 Server IP address range defined in Section 4.3.2.2 2013 Traffic distribution ratio between IPv4 and IPv6 defined in 2014 Section 4.3.1.2 2016 RECOMMENDED cipher suites and key sizes defined in Section 4.3.1.3 2018 Target objective for scenario 1: 50% of the connections per second 2019 measured in benchmarking test TCP/HTTPS Connections per second 2020 (Section 7.6) 2022 Target objective for scenario 2: 50% of the inspected throughput 2023 measured in benchmarking test HTTPS Throughput (Section 7.7) 2025 Initial objective for scenario 1: 10% of Target objective for 2026 scenario 1" (an optional parameter for documentation) 2028 Initial objective for scenario 2: 10% of "Target objective for 2029 scenario 2" (an optional parameter for documentation) 2031 HTTPS transaction per TCP connection: test scenario 1 with single 2032 transaction and the second scenario with 10 transactions 2034 HTTPS with GET command requesting a single object. The RECOMMENDED 2035 object sizes are 1, 16, and 64 KByte. For each test iteration, 2036 client MUST request a single HTTPS response object size. 2038 7.8.3.3. Test Results Validation Criteria 2040 The following test Criteria is defined as test results validation 2041 criteria. Test results validation criteria MUST be monitored during 2042 the whole sustain phase of the traffic load profile. Ramp up and 2043 ramp down phase SHOULD NOT be considered. 2045 a. Number of failed Application transactions (receiving any HTTP 2046 response code other than 200 OK) MUST be less than 0.001% (1 out 2047 of 100,000 transactions) of attempt transactions. 2049 b. Number of Terminated TCP connections due to unexpected TCP RST 2050 sent by DUT/SUT MUST be less than 0.001% (1 out of 100,000 2051 connections) of total initiated TCP connections. 2053 c. During the sustain phase, traffic SHOULD be forwarded at a 2054 constant rate (considered as a constant rate if any deviation of 2055 traffic forwarding rate is less than 5%). 2057 d. Concurrent TCP connections MUST be constant during steady state 2058 and any deviation of concurrent TCP connections SHOULD be less 2059 than 10%. This confirms the DUT opens and closes TCP connections 2060 almost at the same rate. 2062 e. After ramp up the DUT MUST achieve the "Target objective" defined 2063 in the parameter Section 7.8.3.2 and remain in that state for the 2064 entire test duration (sustain phase). 2066 7.8.3.4. Measurement 2068 TTFB (minimum, average and maximum) and TTLB (minimum, average and 2069 maximum) MUST be reported for each object size. 2071 7.8.4. Test Procedures and Expected Results 2073 The test procedure is designed to measure TTFB or TTLB when the DUT/ 2074 SUT is operating close to 50% of its maximum achievable connections 2075 per second or inspected throughput. This test procedure MAY be 2076 repeated multiple times with different IP types (IPv4 only, IPv6 only 2077 and IPv4 and IPv6 mixed traffic distribution), HTTPS response object 2078 sizes and single and multiple transactions per connection scenarios. 2080 7.8.4.1. Step 1: Test Initialization and Qualification 2082 Verify the link status of all connected physical interfaces. All 2083 interfaces are expected to be in "UP" status. 2085 Configure traffic load profile of the test equipment to establish 2086 "Initial objective" as defined in the parameters Section 7.8.3.2. 2087 The traffic load profile can be defined as described in 2088 Section 4.3.4. 2090 The DUT/SUT SHOULD reach the "Initial objective" before the sustain 2091 phase. The measured KPIs during the sustain phase MUST meet all the 2092 test results validation criteria defined in Section 7.8.3.3. 2094 If the KPI metrics do not meet the test results validation criteria, 2095 the test procedure MUST NOT be continued to "Step 2". 2097 7.8.4.2. Step 2: Test Run with Target Objective 2099 Configure test equipment to establish "Target objective" defined in 2100 the parameters table. The test equipment SHOULD follow the traffic 2101 load profile definition as described in Section 4.3.4. 2103 The test equipment SHOULD start to measure and record all specified 2104 KPIs. Continue the test until all traffic profile phases are 2105 completed. 2107 Within the test results validation criteria, the DUT/SUT MUST reach 2108 the desired value of the target objective in the sustain phase. 2110 Measure the minimum, average and maximum values of TFB and TTLB. 2112 7.9. Concurrent TCP/HTTPS Connection Capacity 2114 7.9.1. Objective 2116 Determine the number of concurrent TCP connections that the DUT/SUT 2117 sustains when using HTTPS traffic. 2119 7.9.2. Test Setup 2121 Test bed setup SHOULD be configured as defined in Section 4. Any 2122 specific test bed configuration changes such as number of interfaces 2123 and interface type, etc. MUST be documented. 2125 7.9.3. Test Parameters 2127 In this section, benchmarking test specific parameters SHOULD be 2128 defined. 2130 7.9.3.1. DUT/SUT Configuration Parameters 2132 DUT/SUT parameters MUST conform to the requirements defined in 2133 Section 4.2. Any configuration changes for this specific 2134 benchmarking test MUST be documented. 2136 7.9.3.2. Test Equipment Configuration Parameters 2138 Test equipment configuration parameters MUST conform to the 2139 requirements defined in Section 4.3. Following parameters MUST be 2140 documented for this benchmarking test: 2142 Client IP address range defined in Section 4.3.1.2 2144 Server IP address range defined in Section 4.3.2.2 2145 Traffic distribution ratio between IPv4 and IPv6 defined in 2146 Section 4.3.1.2 2148 RECOMMENDED cipher suites and key sizes defined in Section 4.3.1.3 2150 Target concurrent connections: Initial value from product 2151 datasheet or the value defined based on requirement for a specific 2152 deployment scenario. 2154 Initial concurrent connections: 10% of "Target concurrent 2155 connections" (an optional parameter for documentation) 2157 Connections per second during ramp up phase: 50% of maximum 2158 connections per second measured in benchmarking test TCP/HTTPS 2159 Connections per second (Section 7.6) 2161 Ramp up time (in traffic load profile for "Target concurrent 2162 connections"): "Target concurrent connections" / "Maximum 2163 connections per second during ramp up phase" 2165 Ramp up time (in traffic load profile for "Initial concurrent 2166 connections"): "Initial concurrent connections" / "Maximum 2167 connections per second during ramp up phase" 2169 The client MUST perform HTTPS transaction with persistence and each 2170 client can open multiple concurrent TCP connections per server 2171 endpoint IP. 2173 Each client sends 10 GET commands requesting 1 KByte HTTPS response 2174 objects in the same TCP connections (10 transactions/TCP connection) 2175 and the delay (think time) between each transaction MUST be X 2176 seconds. 2178 X = ("Ramp up time" + "steady state time") /10 2180 The established connections SHOULD remain open until the ramp down 2181 phase of the test. During the ramp down phase, all connections 2182 SHOULD be successfully closed with FIN. 2184 7.9.3.3. Test Results Validation Criteria 2186 The following test Criteria is defined as test results validation 2187 criteria. Test results validation criteria MUST be monitored during 2188 the whole sustain phase of the traffic load profile. 2190 a. Number of failed Application transactions (receiving any HTTP 2191 response code other than 200 OK) MUST be less than 0.001% (1 out 2192 of 100,000 transactions) of total attempted transactions. 2194 b. Number of Terminated TCP connections due to unexpected TCP RST 2195 sent by DUT/SUT MUST be less than 0.001% (1 out of 100,000 2196 connections) of total initiated TCP connections. 2198 c. During the sustain phase, traffic SHOULD be forwarded at a 2199 constant rate (considered as a constant rate if any deviation of 2200 traffic forwarding rate is less than 5%). 2202 7.9.3.4. Measurement 2204 Average Concurrent TCP Connections MUST be reported for this 2205 benchmarking test. 2207 7.9.4. Test Procedures and Expected Results 2209 The test procedure is designed to measure the concurrent TCP 2210 connection capacity of the DUT/SUT at the sustaining period of 2211 traffic load profile. The test procedure consists of three major 2212 steps. This test procedure MAY be repeated multiple times with 2213 different IPv4 and IPv6 traffic distribution. 2215 7.9.4.1. Step 1: Test Initialization and Qualification 2217 Verify the link status of all connected physical interfaces. All 2218 interfaces are expected to be in "UP" status. 2220 Configure test equipment to establish "Initial concurrent TCP 2221 connections" defined in Section 7.9.3.2. Except ramp up time, the 2222 traffic load profile SHOULD be defined as described in Section 4.3.4. 2224 During the sustain phase, the DUT/SUT SHOULD reach the "Initial 2225 concurrent TCP connections". The measured KPIs during the sustain 2226 phase MUST meet the test results validation criteria "a" and "b" 2227 defined in Section 7.9.3.3. 2229 If the KPI metrics do not meet the test results validation criteria, 2230 the test procedure MUST NOT be continued to "Step 2". 2232 7.9.4.2. Step 2: Test Run with Target Objective 2234 Configure test equipment to establish the target objective ("Target 2235 concurrent TCP connections"). The test equipment SHOULD follow the 2236 traffic load profile definition (except ramp up time) as described in 2237 Section 4.3.4. 2239 During the ramp up and sustain phase, the other KPIs such as 2240 inspected throughput, TCP connections per second and application 2241 transactions per second MUST NOT reach to the maximum value that the 2242 DUT/SUT can support. 2244 The test equipment SHOULD start to measure and record KPIs defined in 2245 Section 7.9.3.4. Continue the test until all traffic profile phases 2246 are completed. 2248 Within the test results validation criteria, the DUT/SUT is expected 2249 to reach the desired value of the target objective in the sustain 2250 phase. Follow step 3, if the measured value does not meet the target 2251 value or does not fulfill the test results validation criteria. 2253 7.9.4.3. Step 3: Test Iteration 2255 Determine the achievable concurrent TCP connections within the test 2256 results validation criteria. 2258 8. IANA Considerations 2260 The IANA has assigned IPv4 and IPv6 Address Blocks in [RFC6890] that 2261 have been registered for special purposes. The IPv6 Address Block 2262 2001:2::/48 has been allocated for the purpose of IPv6 Benchmarking 2263 [RFC5180] and the IPv4 Address Block 198.18.0.0/15 has been allocated 2264 for the purpose of IPv4 Benchmarking [RFC2544]. This assignment was 2265 made to minimize the chance of conflict in case a testing device were 2266 to be accidentally connected to part of the Internet. 2268 9. Security Considerations 2270 The primary goal of this document is to provide benchmarking 2271 terminology and methodology for next-generation network security 2272 devices. However, readers should be aware that there is some overlap 2273 between performance and security issues. Specifically, the optimal 2274 configuration for network security device performance may not be the 2275 most secure, and vice-versa. The Cipher suites recommended in this 2276 document are just for test purpose only. The Cipher suite 2277 recommendation for a real deployment is outside the scope of this 2278 document. 2280 10. Contributors 2282 The following individuals contributed significantly to the creation 2283 of this document: 2285 Alex Samonte, Amritam Putatunda, Aria Eslambolchizadeh, David 2286 DeSanto, Jurrie Van Den Breekel, Ryan Liles, Samaresh Nair, Stephen 2287 Goudreault, and Tim Otto 2289 11. Acknowledgements 2291 The authors wish to acknowledge the members of NetSecOPEN for their 2292 participation in the creation of this document. Additionally, the 2293 following members need to be acknowledged: 2295 Anand Vijayan, Baski Mohan, Chao Guo, Chris Brown, Chris Marshall, 2296 Jay Lindenauer, Michael Shannon, Mike Deichman, Ray Vinson, Ryan 2297 Riese, Tim Carlin, and Toulnay Orkun 2299 12. References 2301 12.1. Normative References 2303 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2304 Requirement Levels", BCP 14, RFC 2119, 2305 DOI 10.17487/RFC2119, March 1997, 2306 . 2308 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2309 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2310 May 2017, . 2312 12.2. Informative References 2314 [RFC2544] Bradner, S. and J. McQuaid, "Benchmarking Methodology for 2315 Network Interconnect Devices", RFC 2544, 2316 DOI 10.17487/RFC2544, March 1999, 2317 . 2319 [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., 2320 Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext 2321 Transfer Protocol -- HTTP/1.1", RFC 2616, 2322 DOI 10.17487/RFC2616, June 1999, 2323 . 2325 [RFC2647] Newman, D., "Benchmarking Terminology for Firewall 2326 Performance", RFC 2647, DOI 10.17487/RFC2647, August 1999, 2327 . 2329 [RFC3511] Hickman, B., Newman, D., Tadjudin, S., and T. Martin, 2330 "Benchmarking Methodology for Firewall Performance", 2331 RFC 3511, DOI 10.17487/RFC3511, April 2003, 2332 . 2334 [RFC5180] Popoviciu, C., Hamza, A., Van de Velde, G., and D. 2335 Dugatkin, "IPv6 Benchmarking Methodology for Network 2336 Interconnect Devices", RFC 5180, DOI 10.17487/RFC5180, May 2337 2008, . 2339 [RFC6815] Bradner, S., Dubray, K., McQuaid, J., and A. Morton, 2340 "Applicability Statement for RFC 2544: Use on Production 2341 Networks Considered Harmful", RFC 6815, 2342 DOI 10.17487/RFC6815, November 2012, 2343 . 2345 [RFC6890] Cotton, M., Vegoda, L., Bonica, R., Ed., and B. Haberman, 2346 "Special-Purpose IP Address Registries", BCP 153, 2347 RFC 6890, DOI 10.17487/RFC6890, April 2013, 2348 . 2350 [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol 2351 Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, 2352 . 2354 Appendix A. Test Methodology - Security Effectiveness Evaluation 2356 A.1. Test Objective 2358 This test methodology verifies the DUT/SUT is able to detect, prevent 2359 and report the vulnerabilities. 2361 In this test, background test traffic will be generated in order to 2362 utilize the DUT/SUT. In parallel, the CVEs will be sent to the DUT/ 2363 SUT as encrypted and as well as clear text payload formats using a 2364 traffic generator. The selection of the CVEs is described in 2365 Section 4.2.1. 2367 o Number of blocked CVEs 2369 o Number of bypassed (nonblocked) CVEs 2371 o Background traffic performance (verify if the background traffic 2372 is impacted while sending CVE toward DUT/SUT) 2374 o Accuracy of DUT/SUT statistics in term of vulnerabilities 2375 reporting 2377 A.2. Test Bed Setup 2379 The same Test bed MUST be used for security effectiveness test and as 2380 well as for benchmarking test cases defined in Section 7. 2382 A.3. Test Parameters 2384 In this section, the benchmarking test specific parameters SHOULD be 2385 defined. 2387 A.3.1. DUT/SUT Configuration Parameters 2389 DUT/SUT configuration Parameters MUST conform to the requirements 2390 defined in Section 4.2. The same DUT configuration MUST be used for 2391 Security effectiveness test and as well as for benchmarking test 2392 cases defined in Section 7. The DUT/SUT MUST be configured in inline 2393 mode and all detected attack traffic MUST be dropped and the session 2394 SHOULD be reset 2396 A.3.2. Test Equipment Configuration Parameters 2398 Test equipment configuration parameters MUST conform to the 2399 requirements defined in Section 4.3. The same Client and server IP 2400 ranges MUST be configured as used in the benchmarking test cases. In 2401 addition, the following parameters MUST be documented for this 2402 benchmarking test: 2404 o Background Traffic: 45% of maximum HTTP throughput and 45% of 2405 Maximum HTTPS throughput supported by the DUT/SUT (measured with 2406 object size 64 KByte in the benchmarking tests "HTTP(S) 2407 Throughput" defined in Section 7.3 and Section 7.7. 2409 o RECOMMENDED CVE traffic transmission Rate: 10 CVEs per second 2411 o RECOMMEND to generate each CVE multiple times (sequentially) at 10 2412 CVEs per second 2414 o Ciphers and Keys for the encrypted CVE traffic MUST use the same 2415 cipher configured for HTTPS traffic related benchmarking tests 2416 (Section 7.6 - Section 7.9) 2418 A.4. Test Results Validation Criteria 2420 The following test Criteria is defined as test results validation 2421 criteria. Test results validation criteria MUST be monitored during 2422 the whole test duration. 2424 a. Number of failed Application transaction in the background 2425 traffic MUST be less than 0.01% of attempted transactions. 2427 b. Number of Terminated TCP connections of the background traffic 2428 (due to unexpected TCP RST sent by DUT/SUT) MUST be less than 2429 0.01% of total initiated TCP connections in the background 2430 traffic. 2432 c. During the sustain phase, traffic SHOULD be forwarded at a 2433 constant rate (considered as a constant rate if any deviation of 2434 traffic forwarding rate is less than 5%). 2436 d. False positive MUST NOT occur in the background traffic. 2438 A.5. Measurement 2440 Following KPI metrics MUST be reported for this test scenario: 2442 Mandatory KPIs: 2444 o Blocked CVEs: It SHOULD be represented in the following ways: 2446 * Number of blocked CVEs out of total CVEs 2448 * Percentage of blocked CVEs 2450 o Unblocked CVEs: It SHOULD be represented in the following ways: 2452 * Number of unblocked CVEs out of total CVEs 2454 * Percentage of unblocked CVEs 2456 o Background traffic behavior: it SHOULD be represented one of the 2457 followings ways: 2459 * No impact: considered as "no impact'" if any deviation of 2460 traffic forwarding rate is less than or equal to 5 % (constant 2461 rate) 2463 * Minor impact: considered as "minor impact" if any deviation of 2464 traffic forwarding rate is greater that 5% and less than or 2465 equal to10% (e.g. small spikes) 2467 * Heavily impacted: considered as "Heavily impacted" if any 2468 deviation of traffic forwarding rate is greater that 10% (e.g. 2469 large spikes) or reduced the background HTTP(S) throughput 2470 greater than 10% 2472 o DUT/SUT reporting accuracy: DUT/SUT MUST report all detected 2473 vulnerabilities. 2475 Optional KPIs: 2477 o List of unblocked CVEs 2479 A.6. Test Procedures and Expected Results 2481 The test procedure is designed to measure the security effectiveness 2482 of the DUT/SUT at the sustaining period of the traffic load profile. 2483 The test procedure consists of two major steps. This test procedure 2484 MAY be repeated multiple times with different IPv4 and IPv6 traffic 2485 distribution. 2487 A.6.1. Step 1: Background Traffic 2489 Generate the background traffic at the transmission rate defined in 2490 the parameter section. 2492 The DUT/SUT MUST reach the target objective (HTTP(S) throughput) in 2493 sustain phase. The measured KPIs during the sustain phase MUST meet 2494 all the test results validation criteria defined in Appendix A.4. 2496 If the KPI metrics do not meet the acceptance criteria, the test 2497 procedure MUST NOT be continued to "Step 2". 2499 A.6.2. Step 2: CVE Emulation 2501 While generating the background traffic (in sustain phase), send the 2502 CVE traffic as defined in the parameter section. 2504 The test equipment SHOULD start to measure and record all specified 2505 KPIs. Continue the test until all CVEs are sent. 2507 The measured KPIs MUST meet all the test results validation criteria 2508 defined in Appendix A.4. 2510 In addition, the DUT/SUT SHOULD report the vulnerabilities correctly. 2512 Appendix B. DUT/SUT Classification 2514 This document attempts to classify the DUT/SUT in four different 2515 categories based on its maximum supported firewall throughput 2516 performance number defined in the vendor datasheet. This 2517 classification MAY help user to determine specific configuration 2518 scale (e.g., number of ACL entries), traffic profiles, and attack 2519 traffic profiles, scaling those proportionally to DUT/SUT sizing 2520 category. 2522 The four different categories are Extra Small, Small, Medium, and 2523 Large. The RECOMMENDED throughput values for the following 2524 categories are: 2526 Extra Small (XS) - supported throughput less than or equal to1Gbit/s 2528 Small (S) - supported throughput greater than 1Gbit/s and less than 2529 or equal to 5Gbit/s 2531 Medium (M) - supported throughput greater than 5Gbit/s and less than 2532 or equal to10Gbit/s 2534 Large (L) - supported throughput greater than 10Gbit/s 2536 Authors' Addresses 2538 Balamuhunthan Balarajah 2539 Berlin 2540 Germany 2542 Email: bm.balarajah@gmail.com 2544 Carsten Rossenhoevel 2545 EANTC AG 2546 Salzufer 14 2547 Berlin 10587 2548 Germany 2550 Email: cross@eantc.de 2552 Brian Monkman 2553 NetSecOPEN 2554 417 Independence Court 2555 Mechanicsburg, PA 17050 2556 USA 2558 Email: bmonkman@netsecopen.org