A suggested nomenclature for FortiGate firewall configurations, as first documented by the illustrious /u/VeryStrongBoi in the following thread:
Firewall object naming - What's you standard?
<aside> ⚠️ Note: The following information is for inspiration only. No responsibility is assumed for any configuration implemented based on these suggestions.
</aside>
FortiOS has some limitations regarding lengths of object names, so try to use shorter names or abbreviations, where possible, with the comments fields being used for additional elaborations where needed.
ForitOS runs on Linux, and Linux is case sensitive, so do not mix upper and lower case. The preference should be for all object names to be lower case, except for objects that are by default all upper case, such as service objects, so new/custom service objects should also be all upper case.
White space can create difficulties for parsers for many automation, documentation, and logging systems, so spaces should never be used in object names, and instead dashes - should be used to separate words.
Special characters can also create difficulties for parsers for many systems so the only special characters that should be used in object names are dashes - and underscores _, and never characters like ! @ # $ % ^ & * ( ) ~ + =, etc., even when FortiOS itself allows it.
Unchangeable names (e.g., interfaces) should be named in such a way that they never need to be changed, so they should be named according to their objective essence (which cannot change) rather than their use case (which can change). The alias field (which is changeable) can then be named according to the current use case.
For names which can easily be changed (e.g., address objects) they should be named according to their use case or their FQDN.