Covering your assets

Assets. One of the things that comes to mind at the beginning of a new year is recalling the old and planning for the new… this should include you putting on your asset manager hat.

You may not think you’ve done it before but if you’ve planned for replacing aging items, be they your computer, refrigerator, etc. (you get the point) you’ve maintained an asset list. Now if you’ve never done so for ever what you owned for insurance purposes you should make a detailed list like that ASAP – imagine trying to remember shat you had, models, age, etc. and have to explain them in detail to an insurance adjuster after a disaster…

Now if you’re also a business owner or responsible for tracking technology assets, I’ve got some additional recommendations for you. You should customize this for your needs adding/removing as necessary but the very basics for an asset inventory lists are straight forward: What, where, who, why

  • What is it? 
  • Where is it?
  • Who owns it?
  • Why is it important? (What’s on/in it?)

These will provide at least basic details, and if you’re willing to be, all the info you may need. Imagine a thief stole your television. Can you provide the model number, year purchased, price paid, etc. so that an insurance adjuster can can sider an appropriate replacement?

Here are some basic questions that are more technology based that can help you get started – note there are more details that will also help you plan for compliance questions here:

  • Make of the device (Dell, HP, etc.)
  • Model of the device
  • Serial Number of the device (from manufacturer)
  • Assigned asset tag number (if you use these)
  • Purchase date and cost

Consider adding things like these also

  • Operating System
  • OS version level
  • Business criticality (e.g. Low, Medium, High, Critical)
  • System Name (assigned host name)
  • System Owner  or assigned user/department (who is responsible for the asset, both business and technical contacts)
  • Physical Location
  • Function (apps web server
  • Network location (e.g. internal workstation LAN, DMZ, Protected Internal network, etc.)


If you think of anything else you’d include – drop it in the comments!


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s