One of the convenient aspect of using the prefix “Forti” for product names is that there is less stress to be creative when naming a product do to trying to avoid names that are already taken, trademarked or might otherwise be confused with something else. The drawback is that when coming up with 2 or 3 letter abbreviations the first letter is always going to be the same so as we come up with more products it gets harder to differentiate and match the abbreviation to the product.
Below is a table listing abbreviations that have been associated with Fortinet products. These abbreviations are used for various purposes and sometimes the different abbreviations will be used a different situation for the same product.
- They can be used as part of the model name such as “FGT60D”.
- Some of them will be used as prefixes for the serial number of a product such as “FG100D3G14808602”
- The same prefix syntax used for the serial number may also be used to identify the device in the entries of a syslog server such as “device_id=FG50BH3G09601792”
Some products have been around for some time and the naming convention has evolved over time so that an older model a product may have a different prefix than one of the newer models.
If you need more information about common security terms and acronyms, please refer to the Cookbook glossary.
|FortiADC (Application Delivery Controller)||FAD, FBL|
|FortiAnalyzer||FAZ, FL, FLG|
|FortiAP (Access Point)||FAP|
|FortiCarrier||FCR, FG, FK, FS, FT|
|FortiCarrier, Low Encryption BIOS||LK|
|FortiGate, Low Encryption BIOS||LF|
|FortiMail||FE, FMAIL, FML|
|Fortinet Storage Module||FSM|
|FortiSIEM (Security Information and Event Management)||FSM|
|FortiWAN Load Balancer||FWN|
|FortiWLC (Wireless Controller)||FWC|
Character Code designations
Periodically, a string of characters is added to the name of a product or file to indicate how it is different from the base version. This table is help decipher those little additional characters in the name of something that would otherwise be intuitive to figure out.
|"MI" in the name of a firmware build||Internal build|
|"MN" in the name of a firmware build||North America|