Checklist 2.0 News

The VMFS-3 Virtual Blockade

Filesystem block size rarely enters the sparkling dialog at your noontime geekfest where movie one-liners and song lyrics replace actual conversation but today is different. The ticking of thumbs halts in mid-text when someone at the table opens up an intellectual volley with, “Have you ever seen the error that there isn’t enough space on the filesystem for the selected operation in Virtual Center?” The puzzled faces stare back as if someone had just announced that iPads are on sale for half price. But, before you, or they, have a chance to react to this obviously simple problem of insufficient disk space, the problem isn’t insufficient disk space.

All the years of accepting the default block size when formatting new disks pass before your mind’s eye with curiosity. Don’t decide at this late date that all your efforts were magnetic dust in the wind. All is not lost. Nor are you sentenced to suffer more painful lyric references.

Hitting the Wall

Your SAN Administrator presents you with a fresh 1TB LUN for your VMware environment. You create a new datastore by accepting all the defaults, including the default block size of 1MB. In a few minutes, your 1TB LUN takes on its new role as VMFS-formatted storage for all your space hungry guest systems.

During your first physical to virtual (P2V) migration, you receive a failure notice that looks similar to: “Failed to create virtual disk: There is not enough space on the file system for the selected operation.”

The entire disk capacity of the physical system is 500GB, so how could this happen? You re-examine the physical system’s disk layout and find that, indeed, you have a total capacity of 500GB.

Physical System’s Disk Layout

* C: – 30GB
* E: – 400GB
* F: – 70GB

You attempt the P2V migration a few more times and carefully consider each option as you step through the wizard. However, it fails each time with the same error message.

Block Party

The solution requires that you take notice of what’s happening when you step through the datastore creation wizard. When you reach the Disk/LUN Formatting step, take pause and examine your choices.
The VMFS-3 Virtual Blockade
Disk/LUN Formatting

* 256 GB, Block size: 1 MB
* 512 GB, Block size: 2 MB
* 1024 GB, Block size: 4 MB
* 2048 GB, Block size: 8 MB

Since your E: drive is 400GB in size, and you didn’t resize it during the P2V migration, then you must select a block size of 2MB or larger. Once you do this, the P2V migration will proceed normally. The block sizes and file sizes are limitations of the VMFS-3 filesystem. Yes, limitations. Armed with the knowledge that two whole terabytes should be a single file size large enough for anyone*, it’s also well-known that databases know no such limitations.

VMFS-4 won’t have this limitation. Its maximum file size should follow the ext4 filesystem standard of 16TB.

There are two glaring observations that I can make here. First, it would be great if developers would write errors that are more explicit and more helpful. Generic errors only tend to frustrate technical people into Googling for assistance leading to hours or days of wasted troubleshooting time. Second, shouldn’t VMware move on to VMFS-4 (ext4) or raise the default block size dynamically to the maximum possible for a disk? Feel free to return to your system administrator lunchtime mayhem, chicken strips, fries and Diet Dr. Pepper.

* Sounds a bit like that unattributable quotation, “640K RAM ought to be enough for anyone.” And, like the person who spoke that one into existence, I’ll deny that I ever said it.
Kenneth Hess is a Linux evangelist and freelance technical writer on a variety of open source topics including Linux, SQL, databases, and web services. Ken can be reached via his website at http://www.kenhess.com. Practical Virtualization Solutions by Kenneth Hess and Amy Newman is available now.

Leverage best practices to build effective IT audit plans

We have been getting lot of enquiries on why and how to use best practices to build effective IT audit plans. We thought of publishing this blog to address our approach to building an effective IT audit plan. In order to explain our approach, let’s set the context first:

To understand how best and why to use Best Practices to build effective IT audit plans, we need to put the concept of Best Practices in context and explain our approach.What are Best Practices?
Best Practices evolve, and continue to evolve, over time.  When Best Practices are used under specific conditions or circumstances they will produce the maximum output.  Therefore, we can build an arsenal of Best Practices based on the input of domain experts, vendors and other organizations.

One of the best places to learn the definition for Best Practices is Wikipedia:

  • “A best practice is a technique, method, process, activity, incentive, or reward which conventional wisdom regards as more effective at delivering a particular outcome than any other technique, method, process, etc. when applied to a particular condition or circumstance. The idea is that with proper processes, checks, and testing, a desired outcome can be delivered with fewer problems and unforeseen complications.
  • Best practices can also be defined as the most efficient (least amount of effort) and effective (best results) way of accomplishing a task, based on repeatable procedures that have proven themselves over time for large numbers of people.”

In particular, at Checklist 2.0 we focus on the definition of Best Practices as explained in the second bullet point. Our belief is “Don’t reinvent the wheel”.  Everyone – no matter what their profession – wants to apply the best approach to accomplish a task utilizing the minimum available resources.

In fast changing and complex domains like IT, Best Practices can be leveraged effectively as the underlying technology framework and methodologies.  The IT house is dominated by few major vendors like Microsoft, Oracle, SAP, Google and others. The huge similarities of system installation and functionality requirements by the customer base make Best Practices technology management a huge attraction.  There are several key advantages of having a Best Practices based IT approach is :
1) Benchmarking operations with industry peers to calculate the real return on investment
2) Leverage expensive human capital without time consuming trial and error approach
3) Reduce the total cost of operation by using the collective knowledge of leading edge sources
4) Identify and target well-known gaps or vulnerabilities

How to build multi-dimensional Best Practices
You may understand the value of Best Practices, but the key question is how do you identify, organize and create specific Best Practices to solve business problems and provide end-to-end business solutions?

Best Practices, when captured need to be associated with several dependent factors which would help the consumers to apply and filter based on their specific situation.

For example, a house built in a tropical climate will be designed to reflect the local environment, utilizing local materials, have different a foundation, and connect to local utilities different to a house built in Alaska.  Though each house serves the same purpose, they will vary based on local factors such as climate, weather, local resources and need.

Identifying these different requirements at the beginning and tagging the Best practices based on climatic condition, materials used, plumbings and electrical, local codes, statutes and regulations, etc. is going to help a larger audience to manage and generate specific best practices to be applied during a construction.

Another key factor is the need to keep Best Practices up-to-date.  You may not want to reference a Best Practice white paper published several years ago or read a book outdated even before it goes to press. Building a Best Practices unit which has logical distinction from another unit is the key.  You need to identify and tag the different requirements to build the proper Best Practices.

Who needs to build the Best Practices and when?
In the increasingly connected world the best ideas and practices can come from anywhere. The key to leveraging best practices is to get an up-to-date details of the practices that has several dependency factors and share it globally for users. For example, a doctor in India, where the population is large, operates on at least 10 to 20 patients a day. Best practices used by the doctors to have operate many patients with higher success rate is only can be developed in places like this one. In case of natural disasters in the other part of the world, these practices can be effectively leveraged to handle more number of patients. The key two things to make this process effective is:
1) Sharing of the practices on a global platform
2) Categorizing the practices for different conditions like large number of patients, small number patients etc.,
So, by building a platform to identify, organize, and update Best Practices you will improve efficiency and leverage expertise.

Why IT Audit Planning is using Best Practices
IT Governance and Strategy are critical to an organization’s success.  IT plays a major role in the technology dominated business processes.  A Best Practice based audit plans to evaluate risk uses an 80-20 rule.  This allows you to eliminate all the low-hanging fruit with the global Best Practice knowledge base and helps organizations quickly achieve its desired business objectives. Key to the risk assessment and audit plan process is breaking down the IT Universe into smaller more manageable sub-components. Typically, the IT sub-components are defined as infrastructure, and applications. Contained within the infrastructure sub-component are servers, routers, communications, desktops, etc.
This hardware controls the flow and processing of information throughout the organization. The second sub-component is applications. This is the software used to record and store business transactions. Examples would be database, enterprise resource planning, or business intelligence software.  These controls consist of security applications, disaster recovery
plans, and service level agreements (SLAs).  By leveraging the best practices developed at the sub-components level an IT auditor can quickly build an audit plan based on specific criteria of his/her need and provide a risk assessment report of the IT environment. Checklist 2.0 is built using the principles highlighted above and we would love to hear your thoughts.

IT Auditing Trend – A Google perspective …

An old marketing adage says that a response rate of one half of one percent is a good response to a marketing mailing.  Given such a poor response, is it any surprise that it is difficult to gauge the climate of IT Audit and chart market trends with surveys, feedback and reviews from participants at conferences, meetings and in e-mails?   Several obvious reasons account for this:
1) Participation percentage is low – sampling is based on those who choose to respond.
2) Data is not reliable as participants rarely have real motivation to share their opinions.
3) Survey questions fail to capture many dimensions of a customer’s needs.

This is where big brother Google can help.  Google has made public search terms readily available using a free utility called  Google’s Insights for Search.  With Google Insights for Search, you can compare search volume patterns across geographic regions, subject categories, time frames, and differing sources.  Google Insights for Search produces data based on people’s search patterns, demonstrating customer demand in real-time.

The above chart for demonstrates the response for the search term “IT Audit”.  It tells us the story of how the market for IT Auditing is evolving, revealing market trends.  If you spend some time analysing Rising Searches, Regions and View Change over time, Google Insight provides a wealth of information.  What a great market intelligence tool!

I recently spent some time with the Google Insights for Search tool, and here are some insights I discovered about trends in the market for IT Auditing:

1) Interest in IT audit is declining slowly. I know you don’t want to hear this, but numbers don’t lie.  When SoX was introduced the market for IT Auditing was red hot.  Opportunity was everywhere.  However, as more customers transition from design and implementation of IT controls to more of a maintenance mode, the demand for IT Audit resources has declined.  Additionally, the evolving advancement and complexity of technology has changed the landscape.  Accelerated adoption of inexpensive virtualizied servers and cloud computing is making it tricky for IT auditors.  While security concerns exist and in some cases are on the rise, the management of the cloud computing space creates an environment difficult to navigate from an IT Audit perspective.  This space is managed by the cloud service providers, or the technology behind VMware and other virtualization framework.  The consolidation of computing resources into large cloud farms will ultimately create downward pressure in the IT Audit fees charged by Big 4 auditors.

2) The requirement for IT audit related services are increasing at a breakneck pace outside the U.S.
This is a no-brainer for the people who are up-to-date on the general market trends as GDP is growing approximately 10% per year in the BRIC (Brazil, Russia, India and China) zone and other developing economies. Internal IT demand in these countries is faster than the GDP percentage creating several pockets of demand for IT Audit services.  We can correlate from the Google Insights for Search graph that not a single country on the list is in the developed or more matured economies of the world.  Additionally, growing outsourcing trends to India, the Philippines, and other countries require outsourcing vendors to be compliant with the IT controls requirements of their clients in the U.S. and Western European countries.

3) There is an increasing number of people trying to transition or enter into IT audit marketplace.
A weak job market in developed countries reveals an increasing trend for the number of people seeking jobs in the IT audit.  This will create an interesting situation over the next 2 to 4 years as the IT Audit market is matures.  One trend we can immediately interpret from the chart is there is going to be less and less dedicated IT Auditors, and more multi-skilled or part-time members of our workforce involved in IT Auditing.

4) Demand for Audit Checklists and Best Practices is growing.
Given the speed of technology development, it is not surprising that Google Insights for Search customers predict there will be demand for security audit and checklist requirement in the IT audit domain. At Checklist 2.0, we foresee a continuous sharp surge in the importance of sharing best practices to help build a customizable audit plan. By leveraging the resources of Checklist 2.0 to identify, organize and generate customizable best practices, controls and audit plans to pre-audit, self-assess or audit organizational technology risk areas, our customers are better armed in advance of internal control breakdowns and enable CAEs(Certified Audit Examiners) to initiate audits in those areas.

With these changes evident, what trends do you see which Google Insights for Search has not revealed?  How is the current market climate effecting you and your company?  What impact is virtualization and cloud computing having on you and your company?

Your questions and comments are always welcome.

What makes IT auditing different from traditional auditing

IT Auditing is the process of evaluating and assessing IT assets and processes to insure the implementation of best practices.  IT Audits validate evidence to determine whether IT systems have been designed to effectively and efficiently support an organization.

Traditional auditing is about the evaluation of an organization’s financial systems and processes. The primary objective of traditional auditing is to detect fraud. Traditional auditing focuses mostly on integrity of the financial transactions and compliance to the policies and procedures of an organization.

While IT Audits includes revenue recognition, accounts receivable, and account payables business processes, the audit itself is often automated using some third-party tools or home-grown customized IT applications.

IT audit is a paradigm shift for auditors who are usually involved in traditional auditing.

Traditional auditing is a multi-year, periodic procedure to assess the way organizations carry out their business that impacts the financial statement.

Traditional auditing is time consuming and highly manual.  A financial audit is an intensive project going over several thousand records focusing on compliance of the transactions to organization’s policies.

Traditional auditing is done to ascertain the validity and reliability of information presented to shareholders, investors and regulatory agencies.

In contrast, IT auditing is not often about identifying issues.

Traditional auditing is sometimes expanded to different domains including accounting, quality, energy, etc.

As there are several vendor-based built-in solution or plug-in tools available to identify IT vulnerabilities, it makes sense to use these tools to assess IT environments.

Many IT auditors may not have up-to-date training or expertise for executing a configuration audit of a complex environment such as an ERP (Enterprise Resource Planning) system. The complexity and the variations of IT system implementation render itself for an automated scanner to verify the settings per vendor recommendations, best practices and other standards.
IT auditors need to assess the gaps in policy, processes, and procedures in routine IT tasks including : software development life cycle, access control management, change management, and patch management.

As more and more organizations are moving from implementation of new technologies to more maintenance mode, IT audit focuses not so much on finding problems.
IT audit is focused on fresh look at processes and setup comparing the way the organization’s  IT is run with the industry peers, and the recommended best practices by subject-matter-experts and vendors.

In essence, an end-to-end IT audit identifies opportunities for improvement in implementing best practices and introducing or fine-tuning business policies, processes and procedures. In the case of regulatory compliance, rules governing the law requires an assessment of IT systems internal controls by an independent auditors.

The focus of traditional auditing is financial accounting. Integrity of financial transactions is audited to create a comfort level for the organization’s stakeholder. In IT audit, the focus is only the IT systems that are in scope for the audit objective. As more and more business processes are being automated using sophisticated end-to-end IT systems, IT audit is an integral part of the audit.

Areas Traditional Audit IT Audit
Objective Detect Fraud Assess IT Systems
Scope Financial, Energy, Tax, etc. Technology Practices
Required Expertise Finance, Domain Specific IT & Audit
Approach Risk-based Risk-based and best practices
Method Manual Semi-automated

Isralei financial regulator asks banks to establish policies for social networking

Israeli regulators now require banks to conduct risk assessments and establish clear policies for employee use of social networking websites. This requirement includes that each policy detail which services and sites can be accessed, who can use such sites on behalf of the financial institutions, and how to use them.

‘The use of social networks involves potential dangers to a bank and its customers, including operational, legal, regulatory and reputational risk’, wrote Hizkiyahu in the letter. He highlighted the danger of individuals disseminating false or deceptive information, or impersonating the bank or its employees. The Supervisor further warned that social networking websites are not normally built with a sufficient level of security, raising data security concerns.


Google Apps for Government is FISMA certified now

Google Apps for Government is certified and accredited under the Federal Information Security Management Act (FISMA), which sets security standards for software applications in use by the United States federal government. Google Apps has received an authorization to operate at the FISMA-Moderate level, which is the appropriate level of accreditation for systems that handle sensitive but unclassified (SBU) data – Learn More >>

Auditing Your Auditor

CFO.com has published an interesting article  on audit costs and opportunities for Cost Savings (up to a point).

———————————————————————————–
Auditing Your Auditor

After nearly a decade of turmoil, companies have gained the advantage in negotiating with their auditors.

Click here for the complete article
http://www.cfo.com/article.cfm/14485723/c_14485781

Checklist contributor badge

Oracle Critical Patch Update April 2010

Oracle has released several security related patches to fix the issues in database, fusion middleware and E-business suite applications.  You can find detailed info. of the CPU patch release under:

http://www.oracle.com/technology/deploy/security/critical-patch-updates/cpuapr2010.html

Based on the initial analysis of the patches, OID and Create user components have high CVSS score which warrants DB patch to be rolled out in the critical env.   The good news is – none of these vulnerabilities may be remotely exploitable without authentication, i.e., none may be exploited over a network without the need for a username and password. However, customers need to prioritize the roll out of these patches first to the external facing env. and then to the internal DB env.

Click here to read  Oracle DB best practices

PCI Best Practices

PCI is controversial. As with any business requirement, it has its good parts and bad parts. Too many companies spin their wheels and complain about what they perceive as the negative or unjust parts of PCI. This does not help these companies become compliant or derive value from their compliance efforts. But bottom line, PCI is here to stay. It’s time to move beyond complaining and embrace PCI to extract value. To get started, you must first acknowledge that the set of PCI requirements is really just good, basic security. In fact, PCI incentivizes security. It forces executives to take security seriously and unlocks security budgets. But to really maximize value, security and risk management executives must move beyond the five stages of PCI grief and: 1) shift their mindset to one of proactively embracing PCI; 2) implement PCI as a best practice underlying security framework; and 3) map PCI to other security standards like ISO. We refer to this as “PCI Unleashed.”

Read More >>