Q&A roundup: Mimikatz, thick and thin provisioning, and master data management challenges

| |

We love reading the questions and answers that users post on our site each day. We love that users in the IT Central Station community are willing to devote some time to helping other users by answering questions posted on our site.

This past week, the Q&A topics included (among others) Mimikatz malware, thick and thin provisioning, and common challenges associated with master data management. Here’s a snapshot of some of the answers that our IT Central Station members shared:

What is Mimikatz?

Users shared their knowledge about Mimikatz malware, and made suggestions about how businesses can protect themselves against it. Steve Pender, a Top 20 contributor who is on the Managed Detection and Response (MDR) Leaderboard explained, “Mimikatz is a tool developed by Benjamin Delpy that is used to gather credential data from Windows systems. There are many ways in which an attacker can utilize it. Although some security products block it by its hash or name, this is highly ineffective since anyone can compile Mimikatz as new versions making its hash unknown to reputation services.” Steve recommended SentinelOne as the best solution to protect against this malware. 

Users suggested a number of different ways that businesses can protect themselves against this malware, such as ensuring their Microsoft OS is up to date, using EDR solutions, and implementing multi-factor authentication. 

What is the difference between thick and thin provisioning?

Users provided some really good explanations of thick and thin provisioning. Mark Cruce, a Top 5 Contributor, gave a concise, but clear answer: “Applications require shared block storage to be provisioned. The provisioning is by capacity per LUN (logical unit number) or volume. Thick provisioning means all of the capacity allocated is owned and tied up by that application whether it’s used or not. Unused capacity is not sharable by other applications. Thin provisioning essentially virtualizes the provisioning so the application thinks it has a certain amount of exclusive capacity when in reality, it’s shared. This makes the capacity more flexible and reduces over provisioning.”

What are the biggest challenges in master data management implementation?

The answers to this question were really in-depth – users highlighted common challenges in master data management, and gave advice on how to address these challenges. Some answers focused on the technical challenges (e.g. data quality, and integrating diverse data sources), whereas other answers highlighted the logistics of MDM implementation (e.g. securing funding and endorsement from the business, and earning stakeholder buy-in.)

GaryM, a top 5 contributor, noted, “I have too often witnessed significant resources for planning and committees but in the end fail to deliver anything tangible.  …So my advice is, think big but start small. Triage data based on business impact and level of complexity. Find something simple but with potential high value/impact to the business and just do it. Don’t be afraid to fail – you learn by failing. Just fail small not big.”

Thanks to all the users who are taking the time to ask and answer questions on IT Central Station! 

IT Central Station is here for you, to learn and help your peers. In a market full of vendor hype, we enable you to get real, unbiased information from people like you. 

Do you have a question that you’d like to ask our IT Central Station Community? Ask now!


Q&A roundup: Hybrid vs Multicloud, SIEM, & BPM Processes

Q&A roundup: Continuous Vulnerability Scanning, IT Help Desks and Enterprise Data Analytics Platforms