{"id":11941,"date":"2017-09-06T08:18:38","date_gmt":"2017-09-06T08:18:38","guid":{"rendered":"https:\/\/www.process.st\/templates\/naming-convention-design-servers-computers-it-assets\/"},"modified":"2024-02-28T20:45:07","modified_gmt":"2024-02-28T20:45:07","slug":"naming-convention-design-servers-computers-it-assets","status":"publish","type":"post","link":"https:\/\/www.process.st\/templates\/naming-convention-design-servers-computers-it-assets\/","title":{"rendered":"Naming Convention Design (Servers, Computers, IT Assets)"},"content":{"rendered":"<section id=\"introduction\">\n<h2> Introduction: <\/h2>\n<div class=\"image-content\">\n<figure>\n   <a href=\"https:\/\/www.process.st\/templates\/wp-content\/uploads\/2024\/02\/ifpxeGOTuv4sw8ym2exJAw.png\" alt=\"Introduction:\" target=\"_blank\" rel=\"noopener\"> <img decoding=\"async\" loading=\"lazy\" src=\"https:\/\/www.process.st\/templates\/wp-content\/uploads\/2024\/02\/ifpxeGOTuv4sw8ym2exJAw.png\" \/> <\/a><br \/>\n  <\/figure>\n<\/p><\/div>\n<div class=\"text-content\">\n<p>While many organizations start out naming their devices as Greek gods or fictional characters, it's not scalable in a large organization.<\/p>\n<p>It's better to have a solid naming convention set up than it is to run out of Greek gods when your business starts to bloom.<\/p>\n<p>In this design process, you'll create your own naming conventions for your IT assets that is scalable, readable, standardized and flexible.<\/p>\n<p>To illustrate, here are some diagrams of example naming conventions.<\/p>\n<p><strong><a href=\"https:\/\/www.device42.com\/blog\/2014\/02\/standardizing-host-and-server-naming-conventions\/\" rel=\"nofollow noopener\" target=\"_blank\">Device42 Device Naming Convention<\/a>:<\/strong><\/p>\n<\/p><\/div>\n<div class=\"image-content\">\n<figure>\n   <a href=\"https:\/\/www.process.st\/templates\/wp-content\/uploads\/2024\/02\/vsm8S5RCik5jIfiR2JJFgg.png\" alt=\"\" target=\"_blank\" rel=\"noopener\"> <img decoding=\"async\" loading=\"lazy\" src=\"https:\/\/www.process.st\/templates\/wp-content\/uploads\/2024\/02\/vsm8S5RCik5jIfiR2JJFgg.png\" \/> <\/a><figcaption>\n   <\/figcaption><\/figure>\n<\/p><\/div>\n<div class=\"text-content\">\n<p><a href=\"https:\/\/www.21cii.com\/ITStudio\/Content\/Appendix\/Naming%20Conventions.htm\" rel=\"nofollow noopener\" target=\"_blank\"><strong>21st Century Innovations Device Naming Convention<\/strong><\/a><strong>:<\/strong><\/p>\n<\/p><\/div>\n<div class=\"image-content\">\n<figure>\n   <a href=\"https:\/\/www.process.st\/templates\/wp-content\/uploads\/2024\/02\/he1Wbkk0eoS2Xp_lkx1PIQ.png\" alt=\"Introduction:\" target=\"_blank\" rel=\"noopener\"> <img decoding=\"async\" loading=\"lazy\" src=\"https:\/\/www.process.st\/templates\/wp-content\/uploads\/2024\/02\/he1Wbkk0eoS2Xp_lkx1PIQ.png\" \/> <\/a><br \/>\n  <\/figure>\n<\/p><\/div>\n<div class=\"text-content\">\n<p><strong><a href=\"https:\/\/www.itassetmanagement.net\/2011\/01\/17\/asset-naming-conventions\/\" rel=\"nofollow noopener\" target=\"_blank\">IT Asset Management Device Naming Convention<\/a>:<\/strong><\/p>\n<\/p><\/div>\n<div class=\"image-content\">\n<figure>\n   <a href=\"https:\/\/www.process.st\/templates\/wp-content\/uploads\/2024\/02\/qUqlfamr1zf6AjXLkPNBJA.png\" alt=\"Introduction:\" target=\"_blank\" rel=\"noopener\"> <img decoding=\"async\" loading=\"lazy\" src=\"https:\/\/www.process.st\/templates\/wp-content\/uploads\/2024\/02\/qUqlfamr1zf6AjXLkPNBJA.png\" \/> <\/a><br \/>\n  <\/figure>\n<\/p><\/div>\n<div class=\"text-content\">\n<p>Read on to create your own, or check out this introductory video for more information.<\/p>\n<\/p><\/div>\n<div class=\"video-content\">\n<div class=\"iframe-container\">\n   <iframe src=\"https:\/\/www.youtube.com\/embed\/t_j0Re5KPJw?modestbranding=1&amp;showinfo=0\" frameborder=\"0\" allowfullscreen=\"true\"> <\/iframe>\n  <\/div>\n<\/p><\/div>\n<\/section>\n<section id=\"creating-your-convention\">\n<h2> Creating your convention: <\/h2>\n<div class=\"text-content\">\n<p>Every organization can have its own naming convention. The complexity and variability depends on the size of the organization and its number of devices.<\/p>\n<p>In this section, you'll create a robust and scalable naming convention for an organization of any size.<\/p>\n<\/p><\/div>\n<\/section>\n<section id=\"decide-on-the-key-for-device-location\">\n<h2> Decide on the key for device location <\/h2>\n<div class=\"text-content\">\n<p>Depending on your organization\u2019s size, you might have offices and devices spread out through multiple cities, states, countries, and buildings in the same complex. First, <strong>decide on the first two letters of your naming convention<\/strong>. These can reference the city or office complex the device is located in. For example:<\/p>\n<ul>\n<li><strong>LA<\/strong> (Los Angeles)<\/li>\n<li><strong>AZ<\/strong> (Arizona)<\/li>\n<li><strong>IL<\/strong> (1, Infinite Loop)<\/li>\n<\/ul>\n<p>The next step is to <strong>decide on the third letter<\/strong>. This will be code for the particular building where the device is located.<\/p>\n<p>For each office with devices and multiple buildings, either use existing an existing key or label the buildings A-Z. For offices with single buildings, use just A as a placeholder in case of later expansion. For example:<\/p>\n<ul>\n<li><strong>A<\/strong> = block A<\/li>\n<li><strong>B<\/strong> = block B<\/li>\n<\/ul>\n<p>So far, the prefix for <strong>any device located in your Los Angeles office in block A<\/strong> would be:<\/p>\n<p><strong>LAA<\/strong><\/p>\n<\/p><\/div>\n<div class=\"text-field-content form-field-content\">\n<div class=\"form-group\">\n   <label> Input device location code (ex: LAA) <\/label><br \/>\n   <input type=\"text\" placeholder=\"Something will be typed here...\" disabled=\"disabled\" class=\"form-control\" \/>\n  <\/div>\n<\/p><\/div>\n<\/section>\n<section id=\"add-a-type-section-to-your-device-name-optional\">\n<h2> Add a type section to your device name (optional) <\/h2>\n<div class=\"text-content\">\n<p>If necessary, you can also use a letter to define the type of device.<\/p>\n<p><a href=\"https:\/\/virtualizationreview.com\/blogs\/virtual-insider\/2011\/10\/how-to-design-an-effective-naming-convention.aspx\" rel=\"nofollow noopener\" target=\"_blank\">Virtualization Review<\/a> recommends the following:<\/p>\n<ul>\n<li><strong>V<\/strong>: (Virtual)<\/li>\n<li><strong>C<\/strong>: (Cluster server)<\/li>\n<li><strong>P<\/strong>: (Physical)<\/li>\n<li><strong>O<\/strong>: (Outsourced or vendor supported system)<\/li>\n<\/ul>\n<p>A physical device located in block A of the Los Angeles office would start with:<\/p>\n<p><strong>LAAP<\/strong><\/p>\n<\/p><\/div>\n<div class=\"text-field-content form-field-content\">\n<div class=\"form-group\">\n   <label> Input device type code (ex: V, C, P, O, etc.) <\/label><br \/>\n   <input type=\"text\" placeholder=\"Something will be typed here...\" disabled=\"disabled\" class=\"form-control\" \/>\n  <\/div>\n<\/p><\/div>\n<\/section>\n<section id=\"use-a-delimiter-before-the-variable-portion\">\n<h2> Use a delimiter before the variable portion <\/h2>\n<div class=\"text-content\">\n<p>To improve readability of the device name, use a delimiter to separate the device location from its other specifics.<\/p>\n<p><strong>The<\/strong> <strong>standard delimiter <\/strong>to separate the first half of the name (location, type, team) from the second half (purpose, user, unique ID)<strong> is a dash: -<\/strong><\/p>\n<p>In case your system doesn\u2019t support a dash, you can use another standard character such as # or $.<\/p>\n<p>Example name using the process so far:<\/p>\n<p><strong>LAAP-<\/strong> (A physical device in the A block of your Los Angeles office, with a delimiter in the name)<\/p>\n<p>In the next step, you\u2019ll add information to the 2nd half of the name to make the name unique and more descriptive.<\/p>\n<\/p><\/div>\n<\/section>\n<section id=\"add-the-devices-primary-purpose-to-the-variable-portion\">\n<h2> Add the device\u2019s primary purpose to the variable portion <\/h2>\n<div class=\"text-content\">\n<p><strong>Decide on the primary purpose of all named devices<\/strong>, and their abbreviations.<\/p>\n<p>For example:<\/p>\n<ul>\n<li><strong>DC<\/strong>: Domain Controller<\/li>\n<li><strong>FS<\/strong>: File Server<\/li>\n<li><strong>PS<\/strong>: Print Server<\/li>\n<li><strong>ORA<\/strong>: Oracle database<\/li>\n<li><strong>SQL<\/strong>: SQL database<\/li>\n<li><strong>DB<\/strong>: other database(s)<\/li>\n<li><strong>EXH<\/strong>: Microsoft Exchange<\/li>\n<li><strong>CTX<\/strong>: Citrix Server<\/li>\n<li><strong>ESX<\/strong>: VMware ESX Server<\/li>\n<\/ul>\n<p>For more ideas on efficient device purpose names, see this article from <a href=\"https:\/\/uwaterloo.ca\/information-systems-technology\/about\/organizational-structure\/technology-integrated-services-tis\/network-services-resources\/network-device-naming-standard\" rel=\"nofollow noopener\" target=\"_blank\">University of Waterloo<\/a>.<\/p>\n<p><strong>LAAP-FS<\/strong><\/p>\n<\/p><\/div>\n<div class=\"text-field-content form-field-content\">\n<div class=\"form-group\">\n   <label> Input device purpose code (ex: DB) <\/label><br \/>\n   <input type=\"text\" placeholder=\"Something will be typed here...\" disabled=\"disabled\" class=\"form-control\" \/>\n  <\/div>\n<\/p><\/div>\n<\/section>\n<section id=\"use-a-unique-2digit-id-as-the-last-two-characters\">\n<h2> Use a unique 2-digit ID as the last two characters <\/h2>\n<div class=\"text-content\">\n<p>Office buildings could have multiple physical databases, so it\u2019s important that they are all labelled with a unique ID number.<\/p>\n<p>For example, there can\u2019t be two physical database 01s in your Los Angeles block A (<strong>LAAP-FS01<\/strong>) \u2014 so you name the 2nd one <strong>LAAP-FS02<\/strong>.<\/p>\n<\/p><\/div>\n<div class=\"text-field-content form-field-content\">\n<div class=\"form-group\">\n   <label> Input unique 2-digit ID <\/label><br \/>\n   <input type=\"text\" placeholder=\"Something will be typed here...\" disabled=\"disabled\" class=\"form-control\" \/>\n  <\/div>\n<\/p><\/div>\n<\/section>\n<section id=\"copy-your-new-company-device-name-from-this-task\">\n<h2> Copy your new company device name from this task <\/h2>\n<div class=\"text-content\">\n<p>Using the form fields in this process, you will have built out your company device name. <strong>Find it below<\/strong>:<\/p>\n<p>{{form.Input_device_location_code_(ex:_LAA)}}{{form.Input_device_type_code_(ex:_V,_C,_P,_O,_etc.)}}-{{form.Input_device_purpose_code_(ex:_DB)}}{{form.Input_unique_2-digit_ID}}<\/p>\n<\/p><\/div>\n<\/section>\n<section id=\"validating-your-convention\">\n<h2> Validating your convention: <\/h2>\n<div class=\"text-content\">\n<p>Some systems have specific requirements for naming conventions. For example, Active Directory doesn't allow device names over 15 characters, and some systems have problems with special characters.<\/p>\n<p>In this section, we'll make sure the name is valid with the system you use.<\/p>\n<\/p><\/div>\n<\/section>\n<section id=\"check-the-name-is-unique\">\n<h2> Check the name is unique <\/h2>\n<div class=\"text-content\">\n<p>A naming convention that allows for duplicates is useless. Use a spreadsheet or text pad to identify duplicate lines in your device name list.<\/p>\n<\/p><\/div>\n<\/section>\n<section id=\"check-the-name-is-alphanumeric-if-required\">\n<h2> Check the name is alphanumeric, if required <\/h2>\n<div class=\"text-content\">\n<p>In cases where your system doesn't support non alpha-numeric characters, you may have to remove delimiters and other special characters.<\/p>\n<\/p><\/div>\n<\/section>\n<section id=\"check-the-name-has-no-spaces\">\n<h2> Check the name has no spaces <\/h2>\n<div class=\"text-content\">\n<p>Spaces cause problems with most systems.<\/p>\n<\/p><\/div>\n<\/section>\n<section id=\"adjusting-your-convention-for-personal-devices\">\n<h2> Adjusting your convention for personal devices: <\/h2>\n<div class=\"text-content\">\n<p>Naming conventions can't be one-size-fits-all for every organization. In some cases, you might need to adjust the convention to allow for personal devices (like Joe Bloggs' mobile phone) as well as company devices (like Infinite Loop's C Block Server #43).<\/p>\n<p>The following section will help you adapt your naming convention to allow for both devices.<\/p>\n<\/p><\/div>\n<\/section>\n<section id=\"use-a-unique-username\">\n<h2> Use a unique username <\/h2>\n<div class=\"text-content\">\n<p>Instead of a device\u2019s primary purpose after the delimiter, use the username of the device\u2019s owner, then use the last two characters of the name to specify which kind of device is being named.<\/p>\n<p>For example:<\/p>\n<p><strong>LAAP-BenB-LT<\/strong><\/p>\n<p>Where <strong>BenB<\/strong> is the username, and <strong>LT<\/strong> refers to the user\u2019s laptop.<\/p>\n<p>Suggestions for usernames include:<\/p>\n<ul>\n<li>First name, last initial (<strong>BenB<\/strong>)<\/li>\n<li>First initial, last name (<strong>BBrandall<\/strong>)<\/li>\n<li>First initial, middle initial, last name (<strong>BenJBrandall<\/strong>)<\/li>\n<\/ul><\/div>\n<div class=\"text-field-content form-field-content\">\n<div class=\"form-group\">\n   <label> Input device user's username (RogerSmith) <\/label><br \/>\n   <input type=\"text\" placeholder=\"Something will be typed here...\" disabled=\"disabled\" class=\"form-control\" \/>\n  <\/div>\n<\/p><\/div>\n<\/section>\n<section id=\"add-a-delimiter\">\n<h2> Add a delimiter <\/h2>\n<div class=\"text-content\">\n<p>After the username, another dash should be used to separate the user from the device:<\/p>\n<p><strong>LAAP-BBrandall<\/strong>-<strong>PC-02<\/strong><\/p>\n<p style=\"padding-left: 120px;\"><strong>&nbsp;&nbsp;&nbsp;&nbsp; ^<\/strong><\/p>\n<\/p><\/div>\n<\/section>\n<section id=\"add-a-device-type-code\">\n<h2> Add a device type code <\/h2>\n<div class=\"text-content\">\n<p>Since personal devices are assigned to users, not just physical locations, a username should be tied to <strong>the code of a specific device type<\/strong>. Multiple devices of the same type can be identified with a 2-digit suffix.<\/p>\n<p>Suggestions for device codes include:<\/p>\n<ul>\n<li><strong>LT<\/strong> (Laptop)<\/li>\n<li><strong>PC<\/strong> (Desktop computer)<\/li>\n<li><strong>3D<\/strong> (3D Printer)<\/li>\n<li><strong>MO<\/strong> (Mobile phone)<\/li>\n<li><strong>PJ<\/strong> (Projector)<\/li>\n<li><strong>DP<\/strong> (Desk phone)<\/li>\n<\/ul>\n<p>For Benjamin Brandall's 2nd PC in the Los Angeles Office Block A, the name would be:<\/p>\n<p><strong>LAAP-BBrandall-LT02<\/strong><\/p>\n<\/p><\/div>\n<div class=\"text-field-content form-field-content\">\n<div class=\"form-group\">\n   <label> Add personal device type code (ex. LT, PJ, etc.) <\/label><br \/>\n   <input type=\"text\" placeholder=\"Something will be typed here...\" disabled=\"disabled\" class=\"form-control\" \/>\n  <\/div>\n<\/p><\/div>\n<div class=\"text-field-content form-field-content\">\n<div class=\"form-group\">\n   <label> Input unique 2-digit ID for the personal device <\/label><br \/>\n   <input type=\"text\" placeholder=\"Something will be typed here...\" disabled=\"disabled\" class=\"form-control\" \/>\n  <\/div>\n<\/p><\/div>\n<\/section>\n<section id=\"copy-your-new-personal-device-name-from-this-task\">\n<h2> Copy your new personal device name from this task <\/h2>\n<div class=\"text-content\">\n<p>The name below is aggregated from the form fields so far in the process:<\/p>\n<p>{{form.Input_device_location_code_(ex:_LAA)}}{{form.Input_device_type_code_(ex:_V,_C,_P,_O,_etc.)}}-{{form.Input_device_user's_username_(RogerSmith)}}-{{form.Add_personal_device_type_code_(ex._LT,_PJ,_etc.)}}{{form.Input_unique_2-digit_ID_for_the_personal_device}}<\/p>\n<\/p><\/div>\n<\/section>\n<section id=\"sources\">\n<h2> Sources: <\/h2>\n<div class=\"text-content\">\n<ul>\n<li><a href=\"https:\/\/serverdensity.com\/\" rel=\"nofollow noopener\" target=\"_blank\">Server Density<\/a> - <a href=\"https:\/\/blog.serverdensity.com\/server-naming-conventions-and-best-practices\/\" rel=\"nofollow noopener\" target=\"_blank\">Server Naming Conventions<\/a><\/li>\n<li><a href=\"https:\/\/www.device42.com\/\" rel=\"nofollow noopener\" target=\"_blank\">Device42<\/a> - <a href=\"https:\/\/www.device42.com\/blog\/2014\/02\/standardizing-host-and-server-naming-conventions\/\" rel=\"nofollow noopener\" target=\"_blank\">Standardizing Host and Server Naming Conventions<\/a><\/li>\n<li><a href=\"https:\/\/www.itassetmanagement.net\/\" rel=\"nofollow noopener\" target=\"_blank\">IT Asset Management<\/a> - <a href=\"https:\/\/www.itassetmanagement.net\/2011\/01\/17\/asset-naming-conventions\/\" rel=\"nofollow noopener\" target=\"_blank\">IT Asset Naming Conventions<\/a><\/li>\n<li><a href=\"https:\/\/www.21cii.com\/\" rel=\"nofollow noopener\" target=\"_blank\">21st Century Innovations Inc. <\/a>- <a href=\"https:\/\/www.21cii.com\/ITStudio\/Content\/Appendix\/Naming%20Conventions.htm\" rel=\"nofollow noopener\" target=\"_blank\">Naming Conventions<\/a><\/li>\n<li><a href=\"https:\/\/uwaterloo.ca\/\" rel=\"nofollow noopener\" target=\"_blank\">University of Waterloo<\/a> - <a href=\"https:\/\/uwaterloo.ca\/information-systems-technology\/about\/organizational-structure\/technology-integrated-services-tis\/network-services-resources\/network-device-naming-standard\" rel=\"nofollow noopener\" target=\"_blank\">Network device naming standards<\/a><\/li>\n<li><a href=\"https:\/\/virtualizationreview.com\" rel=\"nofollow noopener\" target=\"_blank\">Virtualization Review<\/a> - <a href=\"https:\/\/virtualizationreview.com\/blogs\/virtual-insider\/2011\/10\/how-to-design-an-effective-naming-convention.aspx\" rel=\"nofollow noopener\" target=\"_blank\">How To Design An Effective Naming Convention<\/a><\/li>\n<\/ul><\/div>\n<\/section>\n<section id=\"related-checklists\">\n<h2> Related checklists: <\/h2>\n<div class=\"text-content\">\n<ul>\n<li><a href=\"https:\/\/www.process.st\/templates\/cisco-router-setup\/\" rel=\"nofollow\">Cisco Router Setup<\/a><\/li>\n<li><a href=\"https:\/\/www.process.st\/templates\/vendor-management-supplier-evaluation\/\" rel=\"nofollow\">Vendor Management: Supplier Evaluation<\/a><\/li>\n<li><a href=\"https:\/\/www.process.st\/templates\/vendor-management-contract-negotiation\/\" rel=\"nofollow\">Vendor Management: Contract Negotiation<\/a><\/li>\n<li><a href=\"https:\/\/www.process.st\/templates\/it-service-call-process\/\" rel=\"nofollow\">IT Service Call Process<\/a><\/li>\n<li><a href=\"https:\/\/www.process.st\/templates\/scheduled-maintenance-notification\/\" rel=\"nofollow\">Scheduled Maintenance Notification<\/a><\/li>\n<li><a href=\"https:\/\/www.process.st\/templates\/patch-management\/\" rel=\"nofollow\">Patch Management<\/a><\/li>\n<li><a href=\"https:\/\/www.process.st\/templates\/network-security-management\/\" rel=\"nofollow noopener\" target=\"_blank\">Network Security Management<\/a><\/li>\n<li><a href=\"https:\/\/www.process.st\/templates\/client-data-backup-best-practices\/\" rel=\"nofollow noopener\" target=\"_blank\">Client Data Backup Best Practices<\/a><\/li>\n<li><a href=\"https:\/\/www.process.st\/templates\/computer-maintenance-guide\/\" rel=\"nofollow noopener\" target=\"_blank\">Computer Maintenance Guide<\/a><\/li>\n<li><a href=\"https:\/\/www.process.st\/templates\/inventory-management-process\" rel=\"nofollow noopener\" target=\"_blank\">Inventory Management Process<\/a><\/li>\n<li><a href=\"https:\/\/www.process.st\/templates\/ubuntu-server-setup-process\/\" rel=\"nofollow noopener\" target=\"_blank\">Server Setup Process<\/a><\/li>\n<li><a href=\"https:\/\/www.process.st\/templates\/virtual-private-server-setup\/\" rel=\"nofollow noopener\" target=\"_blank\">Virtual Private Server Setup<\/a><\/li>\n<li><a href=\"https:\/\/www.process.st\/templates\/it-support-process\/\" rel=\"nofollow noopener\" target=\"_blank\">IT Support Process<\/a><\/li>\n<li><a href=\"https:\/\/www.process.st\/templates\/helpdesk-management\/\" rel=\"nofollow noopener\" target=\"_blank\">Helpdesk Management<\/a><\/li>\n<li><a href=\"https:\/\/www.process.st\/templates\/server-maintenance-checklist\/\" rel=\"nofollow noopener\" target=\"_blank\">Server Maintenance Checklist<\/a><\/li>\n<li><a href=\"https:\/\/www.process.st\/templates\/server-security-checklist\/\" rel=\"nofollow noopener\" target=\"_blank\">Server Security Checklist<\/a><\/li>\n<li><a href=\"https:\/\/www.process.st\/templates\/information-security-incident-response\/\" rel=\"nofollow noopener\" target=\"_blank\">Information Security Incident Response<\/a><\/li>\n<li><a href=\"https:\/\/www.process.st\/templates\/sql-server-audit-checklist\/\" rel=\"nofollow noopener\" target=\"_blank\">SQL Server Audit Checklist<\/a><\/li>\n<li><a href=\"https:\/\/www.process.st\/templates\/privileged-password-management\/\" rel=\"nofollow noopener\" target=\"_blank\">Privileged Password Management<\/a><\/li>\n<li><a href=\"https:\/\/www.process.st\/templates\/network-administrator-daily-tasks\/\" rel=\"nofollow noopener\" target=\"_blank\">Network Administrator Daily Tasks<\/a><\/li>\n<li><a href=\"https:\/\/www.process.st\/templates\/network-security-audit-checklist\/\" rel=\"nofollow noopener\" target=\"_blank\">Network Security Audit Checklist<\/a><\/li>\n<li><a href=\"https:\/\/www.process.st\/templates\/firewall-audit-checklist\/\" rel=\"nofollow noopener\" target=\"_blank\">Firewall Audit Checklist<\/a><\/li>\n<li><a href=\"https:\/\/www.process.st\/templates\/vpn-configuration\/\" rel=\"nofollow noopener\" target=\"_blank\">VPN Configuration<\/a><\/li>\n<li><a href=\"https:\/\/www.process.st\/templates\/setup-apache-server\/\" rel=\"nofollow noopener\" target=\"_blank\">Apache Server Setup<\/a><\/li>\n<li><a href=\"https:\/\/www.process.st\/templates\/email-server-security\/\" rel=\"nofollow noopener\" target=\"_blank\">Email Server Security<\/a><\/li>\n<li><a href=\"https:\/\/www.process.st\/templates\/penetration-testing\/\" rel=\"nofollow noopener\" target=\"_blank\">Penetration Testing<\/a><\/li>\n<\/ul><\/div>\n<\/section>\n","protected":false},"excerpt":{"rendered":"<p>Introduction: While many organizations start out naming their devices as Greek gods or fictional characters, it's not scalable in a large organization. It's better to have a solid naming convention set up than it is to run out of Greek gods when your business starts to bloom. In this design process, you'll create your own [&hellip;]<\/p>\n","protected":false},"author":3,"featured_media":11942,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"ep_exclude_from_search":false,"cover_icon_emoji":"","cover_icon_url":"","tasks_count":"19","template_description":"How to design and use a scalable, robust naming convention for your organization and clients.","template_id":"nI9gPhl08ZVoLpbOemlL3w","task_0":"Introduction:","task_slug_0":"introduction","task_1":"Creating your convention:","task_slug_1":"creating-your-convention","task_2":"Decide on the key for device location","task_slug_2":"decide-on-the-key-for-device-location","task_3":"Add a type section to your device name (optional)","task_slug_3":"add-a-type-section-to-your-device-name-optional","task_4":"Use a delimiter before the variable portion","task_slug_4":"use-a-delimiter-before-the-variable-portion","task_5":"Add the device\u2019s primary purpose to the variable portion","task_slug_5":"add-the-devices-primary-purpose-to-the-variable-portion","task_6":"Use a unique 2-digit ID as the last two characters","task_slug_6":"use-a-unique-2digit-id-as-the-last-two-characters","task_7":"Copy your new company device name from this task","task_slug_7":"copy-your-new-company-device-name-from-this-task","task_8":"Validating your convention:","task_slug_8":"validating-your-convention","task_9":"Check the name is unique","task_slug_9":"check-the-name-is-unique","task_10":"Check the name is alphanumeric, if required","task_slug_10":"check-the-name-is-alphanumeric-if-required","task_11":"Check the name has no spaces","task_slug_11":"check-the-name-has-no-spaces","task_12":"Adjusting your convention for personal devices:","task_slug_12":"adjusting-your-convention-for-personal-devices","task_13":"Use a unique username","task_slug_13":"use-a-unique-username","task_14":"Add a delimiter","task_slug_14":"add-a-delimiter","task_15":"Add a device type code","task_slug_15":"add-a-device-type-code","task_16":"Copy your new personal device name from this task","task_slug_16":"copy-your-new-personal-device-name-from-this-task","task_17":"Sources:","task_slug_17":"sources","task_18":"Related checklists:","task_slug_18":"related-checklists","task_19":"","task_slug_19":"","task_20":"","task_slug_20":"","task_21":"","task_slug_21":"","task_22":"","task_slug_22":"","task_23":"","task_slug_23":"","task_24":"","task_slug_24":"","task_25":"","task_slug_25":"","task_26":"","task_slug_26":"","task_27":"","task_slug_27":"","task_28":"","task_slug_28":"","task_29":"","task_slug_29":"","task_30":"","task_slug_30":"","task_31":"","task_slug_31":"","task_32":"","task_slug_32":"","task_33":"","task_slug_33":"","task_34":"","task_slug_34":"","task_35":"","task_slug_35":"","task_36":"","task_slug_36":"","task_37":"","task_slug_37":"","task_38":"","task_slug_38":"","task_39":"","task_slug_39":"","task_40":"","task_slug_40":"","task_41":"","task_slug_41":"","task_42":"","task_slug_42":"","task_43":"","task_slug_43":"","task_44":"","task_slug_44":"","task_45":"","task_slug_45":"","task_46":"","task_slug_46":"","task_47":"","task_slug_47":"","task_48":"","task_slug_48":"","task_49":"","task_slug_49":"","task_50":"","task_slug_50":"","task_51":"","task_slug_51":"","task_52":"","task_slug_52":"","task_53":"","task_slug_53":"","task_54":"","task_slug_54":"","task_55":"","task_slug_55":"","task_56":"","task_slug_56":"","task_57":"","task_slug_57":"","task_58":"","task_slug_58":"","task_59":"","task_slug_59":"","task_60":"","task_slug_60":"","task_61":"","task_slug_61":"","task_62":"","task_slug_62":"","task_63":"","task_slug_63":"","task_64":"","task_slug_64":"","task_65":"","task_slug_65":"","task_66":"","task_slug_66":"","task_67":"","task_slug_67":"","task_68":"","task_slug_68":"","task_69":"","task_slug_69":"","task_70":"","task_slug_70":"","task_71":"","task_slug_71":"","task_72":"","task_slug_72":"","task_73":"","task_slug_73":"","task_74":"","task_slug_74":"","task_75":"","task_slug_75":"","task_76":"","task_slug_76":"","task_77":"","task_slug_77":"","task_78":"","task_slug_78":"","task_79":"","task_slug_79":"","task_80":"","task_slug_80":"","task_81":"","task_slug_81":"","task_82":"","task_slug_82":"","task_83":"","task_slug_83":"","task_84":"","task_slug_84":"","task_85":"","task_slug_85":"","task_86":"","task_slug_86":"","task_87":"","task_slug_87":"","task_88":"","task_slug_88":"","task_89":"","task_slug_89":"","task_90":"","task_slug_90":"","task_91":"","task_slug_91":"","task_92":"","task_slug_92":"","task_93":"","task_slug_93":"","task_94":"","task_slug_94":"","task_95":"","task_slug_95":"","task_96":"","task_slug_96":"","task_97":"","task_slug_97":"","task_98":"","task_slug_98":"","task_99":"","task_slug_99":"","footnotes":""},"categories":[42,7,1],"tags":[],"class_list":["post-11941","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-internal-audit","category-miscellaneous","category-uncategorized"],"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/posts\/11941","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/comments?post=11941"}],"version-history":[{"count":0,"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/posts\/11941\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/media\/11942"}],"wp:attachment":[{"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/media?parent=11941"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/categories?post=11941"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/tags?post=11941"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}