One Article Review
| Source |  AlienVault Blog |
|---|---|
| Identifiant | 1417761 |
| Date de publication | 2019-10-21 13:00:00 (vue: 2019-10-21 16:06:44) |
| Titre | Reviewing best practices for IT asset management in the cloud |
| Texte |
It used to be that businesses needing their own large computer networks had to do everything themselves. They had to buy all of their servers, all of their networking appliances. They needed the physical space on premises for all of their datacenters, the HVAC people to keep everything cool, and the massive electricity bills to keep all of that going.
But in the past several years, the growth of cloud services has been exponential. It’s great for the enterprise because depending on a business’s specific needs, they can either have everything but their local area network on the cloud, or they can have some hybrid of their own on premises network and a cloud provider or two, fully integrated. Either way, they can put at least some of their networking needs in the hands of a cloud provider such as AWS, Microsoft Azure, or Google Cloud. That can save a company a lot of time, labor, space, and money. Plus, the agility and flexibility that cloud providers offer is great! Do you need to double the data capacity of your network as soon as possible? It’s much quicker and easier to change your cloud provider plan and do some adjustments on your end than it is to double the size of your on prem network. The cloud can be a lifesaver, but your IT people still need to know how to manage their computing assets there, especially when it comes to cybersecurity. Cloud asset management is a special matter, and it’s absolutely vital to understand.
What is cloud asset management?
Your IT assets are the hardware, software, and networking entities that your company has as tools and resources for their objectives. An excellent example of an IT asset is a database. Databases are very important, particularly in the backend of your applications.
With the implementation of cloud networks, these IT assets become cloud assets too. So instead of having your MySQL databases entirely on your on premises servers and data storage, you can have them run from the server and data storage capacity that your cloud provider offers your business.
But making sure your cloud-hosted assets function well and maintain security is its own area of knowledge: cloud asset management. There are challenges involved in cloud asset management which differ from managing assets on your own infrastructure. For instance, developers and administrators often don’t use the security tools that their cloud providers offer them. Also, visibility into your assets can be more difficult in the cloud. You can’t secure what you can’t see!
Cloud asset management best practices
There’s a lot to learn when it comes to cloud asset management. It can seem overwhelming to start. Thankfully, there are some best practices to keep in mind which will provide you with a strong foundation for properly handling the cloud.
Monitor your cloud as thoroughly as possible
As I mentioned, visibility in cloud networks can be a special challenge. There’s also the everyday performance of your network to consider. You won’t be physically inside of your cloud provider’s datacenter, so you’ll need to be able to see as much as possible with monitoring tools. This isn’t all directly security related. You need to make sure that your provider honors your Service Level Agreement. Watch your bandwidth and make sure that it suits your organization’s needs at all times. Make sure all of your cloud assets have excellent availability, as much uptime as possible. You could have thousands of users depending on your cloud at any given second. Monitor thoroughly and constantly to make sure that your cloud is always capable and reliable.
Redundancy and automation are your friends
Redundancy goes a long way when it comes to keeping good uptime and everything working properly. There should be as few single points of failure as possible, preferably no |
| Envoyé | Oui |
| Condensat | able about absolutely access adjustments administrators agile agility agreement all also always any appliances applicable application applications are area aren’t asset assets attacks automated automation availability avoidable aws azure backend backups bandwidth because become been being beings benefits best bettercloud big bills both business business’s businesses but buy can can’t capable capacity cases challenge challenges change choose choosing cloud cloudsploit coding combine combining comes company completely computer computers computing conclusion configuration consider constantly cool costs could cyber cybersecurity data database databases datacenter datacenters depending develop developers dictates differ difference different difficult directly disasters don’t double each easier efficient either electrical electricity employees end entail enterprise entirely entities environments error especially everyday everything example excellent experts exponential extra facilitate failure features figure first flexibility foundation friends from fully function functionality github given goes going good google great growth had handling hands hardware has have having helps here honors host hosted how human hvac hybrid implement implementation implemented important include infrastructure inside instance instead integrated inventory involved isn’t issues it’s its just keep keeping key know knowledge: labor large leading learn least level lifesaver local long lot maintain make makes making manage managed management managing manifest many massive matter may mentioned microsoft mind mitigates money monitor monitoring more much multi multiple mysql natural need needed needing needs network networking networks none objectives occur offboarding offer offers often onboarding open operations option oracle order organization’s organizations other out outages overwhelming own particular particularly past people perform performance physical physically plan plans platform platforms plenty plus points policies possibilities possibility possible practices preferably prem premises prepared pretty principles privileged problems procedures process properly protection provide provider provider’s providers provides put quicker recommend reduce redundancy related reliable reliably repetition repetitive resources reviewing right risk risks run saas save saves second secure security see seem server servers service services several should single sites size software some soon source space special specific start storage strong such suits sure tasks tedious tedium tested than thankfully that’s them themselves there’s these thoroughly thousands time times too tool tools touted trained tricky two understand uptime use used user users very visibility vital watch way ways well what when which will won’t working works years you’ll your |
| Tags | Tool Guideline |
| Stories | |
| Notes | ★★★★★ |
| Move | 
|
L'article ne semble pas avoir été repris aprés sa publication.
L'article ne semble pas avoir été repris sur un précédent.