Home > Intel Communities > Open Port IT Community > IT@Intel > Blog
1 2 3 ... 10 Previous Next

IT@Intel Blog

141 Posts
0

Let me begin by way of introduction - I am a strategic financial analyst with Intel IT Finance organization focused on data center strategy and efficiency efforts.  This is my maiden voyage into the world of blogging, so I hope the topic is relevant and interesting to the audience.

Similar to many organizations, Intel IT is focused on constantly improving the cost of keeping the business running while not sacrificing the level of support required by customers.  With industry and technology solutions evolving at an increasing pace, choosing the most appropriate place and time to invest is paramount to driving down infrastructure costs.  Budget constraints in this economic climate and the make implementing efficiency efforts all the more daunting.

In 2008, Intel IT initiated a Design Server Refresh strategy where the basic premise was to leverage server performance improvements to respond to increasing compute requirements without growing data center capacity at a corresponding rate.  In 2008, we were able to remove 20,000 single core servers from our production environment, allowing us to realize approximately $45M savings through avoiding data center additions and server operating costs.  However, even with this strategy driving significant near term results, the 2009 operating environment forced us to pause and re-evaluate the merits of continuing execution to the strategy.

This re-evaluation concluded that this was an investment that couldn't be deferred due to the need for incremental growth and the high utilization of our existing data centers.  In addition, based on a average 10:1 consolidation, the refresh of single core servers would generate significant operating savings and clear more headroom than seen historically.  The details of this analysis are included in the White Paper:  Staying Committed to Server Refresh Reduces Cost

Questions for the readers: Do others have a refresh strategy or guideline? Are others seeing this type of impact/results and the challenges in implementation?

0 Comments Permalink
0

I was recently trading thoughts with Anton Chuvakin, a respected security metrics professional, in a philosophical discussion of perfection and quality of security.  Admittedly, I was on auto-pilot (operating without the benefit of coffee) rattling away with my ‘Optimal Security’ rhetoric, when Anton posed two thought provoking questions: CAN one "mandate optimal security"?  How do you "mandate flexible"?

 

I was stopped in my tracks.  This got me thinking.  After fetching a tall cup of coffee to start my brain juices flowing in earnest, I reached back into the pages of history to come up with the following perspective and examples:

 

I believe, to a certain extent, we can mandate flexibility and optimization.  Surely we can act in ways which deny both.  So why can’t we act in a manner which intrinsically promotes them?

 

I think back to lessons of WWII and the Maginot line.  The French chose to create a fortification which was static by design and lacked mobility or a capability to adapt to changing enemy tactics.  They invested heavily into this control, which became the backbone of their country's eastern defense.  It was an appalling failure.  Alternatively, the German blitzkrieg, and the stratagems of both Rommel and Patton prevailed.  Flexibility through mobility was far more effective than an elaborate static defense.

 

I would argue that flexibility can be mandated through proper planning and design.  We have examples in the history of information security.  In the early years of Anti-Virus (AV) products, they were non-memory resident applications which were prescribed to be run once a week.  Updates were a rarity if at all.  That rigid design quickly lost effectiveness, with the rise in velocity of new malware.  AV vendors were forced to adapt.  The overall design has changed to one which is flexible, can be updated to meet emerging malware, and continuously runs in the background to provide persistent security.

 

Rigid security postures lack the ability to remain effective over time and are likely derived by an equally rigid infrastructure which will struggle to adapt to new threats and changes within the organization.  Create security to be flexible and you enable the service to keep up with the continual changes.

 

In general, design a system to be flexible and its longevity for effectiveness is extended.  Plan how systems can continuously adjust itself to align to what is 'optimal' and you increase the sustaining efficiency.

 

We must be strategic in our planning and design of security, lest we suffer the fate of France's Maginot line.

 


Check out Anton’s Blog for other thought provoking viewpoints; just be sure to have your coffee at the ready.

More on “Optimal security”:

Strategy for Sustaining Optimal Security

Information Security Defense In Depth Whitepaper is Now Available

Fortune Cookie Security Advice - June 2008

Defense In Depth Strategy Optimizes Security

The Four Dirty Questions of Measuring Information Security


What are your thoughts?  Rigid or Fluid?  Have you implemented optimal and flexible?

0 Comments Permalink
0

Think strategic.  Act competitive.  Be secure.

 

Everyone wants information security to be easy.  Wouldn’t it be nice if it were simple enough to fit snugly inside a fortune cookie?  Well, although I don’t try to promote such foolish nonsense, I do on occasion pass on readily digestible nuggets to reinforce security principles and get people thinking how security applies to their environment.

 

The key to fortune cookie advice is ‘common sense’ in the context of security.  It must be simple, succinct, and make sense to everyone, while conveying important security aspects.

 


Fortune Cookie advice for June, 2009:

 

 

Strategy.gif

Think strategic.  Act competitive.  Be secure.

 

Security is a sustaining commitment where long term planning provides a distinct advantage.  Threats are derived from intelligent adversaries.  Success requires maneuvering in a competitive manner to remain secure.

 

 

 

 

Fortune Cookie Security Advice - May 2008

Fortune Cookie Security Advice - June 2008

Fortune Cookie Security Advice - August 2008

Fortune Cookie Security Advice - September 2008

Fortune Cookie Security Advice - November 2008

Fortune Cookie Security Advice - December 2008

Fortune Cookie Security Advice - January 2009

Fortune Cookie Security Advice - February 2009

Fortune Cookie Security Advice - March 2009

Fortune Cookie Security Advice - April 2009

Fortune Cookie Security Advice - May 2009

0 Comments Permalink
0

Optimal security must not only be attained, but also sustained over time.  A good security strategy must be forward thinking to understand how intervention and continual maintenance will be needed, then implement those capabilities as part of a complete service deployment.

 

Balance.gif

'Optimal Security' is the right balance of security spending and losses prevented where business acceptable losses are achieved.  It changes often and likely maintains different targets for the dissimilar parts of the entity.

 

Organizations are likely to mandate security expectations which typically manifests in a set of configurations, specifications, and operating standards.  The risk is these security controls may be relatively static and entrenched.

 

Establishing a baseline security is a good practice, but in order to remain effective it must adapt to changes in the environment by remaining dynamic to keep in lock-step with rapidly changing threats, vulnerabilities, and resulting exposures.  It must be a fluid posture, able to rapidly change based upon different internal priorities and external changes.  Sustaining business structure must be designed to continually predict areas needing modification and support design and deployment of those changes.  Rigid security postures lack the ability to remain effective over time and are likely derived by an equally rigid infrastructure which will struggle to adapt to new threats and changes within the organization.  Design security to be flexible and you enable the service to keep up with the continual changes in the information branch of security.

 

I recently spoke with an organization who had established a security posture which relied heavily on a hardened OS and application build for their systems.  At the time, they deployed a platform which took into consideration all the best configurations for hardening.  They were so confident they had satisfied security requirements they considered the problem solved.  They integrated the security design into their normal platform refresh cycle of system replacement every few years.  They never comprehended the fact they would need to continually update the build to compensate for changes in threats, new vulnerabilities and malware, and evolving business usage models.

 

The platform’s security, which initially was strong, began to quickly erode.  With no internal mechanism to identify when changes needed to be made, nor the testing and distribution capability, they soon found themselves in a situation where they were responding to individual incidents and changing systems one at a time based upon particular end-user needs.  This created inconsistencies in the builds which was more difficult to support.  Without proper forethought, the security team turned themselves into a firefighting organization, losing the initiative in the war of security.

 

This is one simple technical example.  The same holds true for the expanse of automated solutions and behavioral security controls as well.  Highly effective and efficient security strategies are forward thinking and understand how intervention and continual maintenance will be needed, then implement those capabilities as part of a complete service deployment.  Overall, the concept of ‘optimal security’ is one of fluid adaptations of controls to meet an ever changing target for risk acceptance.

0 Comments Permalink
0

 

Back in April I told you about a small proof of concept we were planning to measure energy use in the office environment and then use that established baseline to test different energy saving methods.  I thought it would be good to give you a quick status update on the work done to date.

 

The PoC is currently underway, and in fact, is nearing completion.  Like I mentioned in April, it is pretty small with just 12 users, but we hope the results will help direct what we might later try on a larger scale.

 

We started the PoC on Friday May 15th with meter loggers installed on 6 circuits monitoring energy use for the 12 users in the PoC every 3 minutes.  We ran the metering for 2 weeks before telling the PoC users to establish an uninfluenced baseline.

 

After setting the baseline, we split the 12 users in to 3 groups, each focusing on a different energy savings technique.

 

One group receives information on their energy use every 2 days showing how much energy they are using, what it is costing, and a few simple tips on how they might reduce their energy use.  Nothing is forced.  In this group, we are looking at how “Awareness” alone might change behavior.

 

The second group installed a 3rd party agent on their systems which allows us to enforce more restrictive energy management profiles than they might normally use.  The software also allows us to record time in state on each system, thereby providing a degree of “soft” individual system metering.

 

The last group had USB triggered power strips installed in their offices, connected to their docking stations, which automatically power off all devices in their offices that do not need to be on when they are not there.  We connected devices such as; task lighting, displays, and chargers to these strips.

 

We are in the last week of data collecting now, so stay tuned for some high-level results to be posted soon and possibility a full paper published later.

 

Please let me know if you have any questions or if you are doing or have done anything similar in your enterprise.

 

-Mike

0 Comments Permalink
0

As a major global manufacturer Intel works constantly to improve its Supply Chain. Our ERP implementation and key projects are integral ingredients in the process of driving Supply Chain improvements. It was exciting that recently we saw Intel recognized as one of the top leading companies from a Supply Chain perspective. AMR Research published The AMR Research Supply Chain Top 25 for 2009.

 

Check out AMR’s Press release:

http://www.amrresearch.com/Content/View.aspx?compURI=tcm%3a7-43474&title=AMR+Research+Releases+Its+2009+Supply+Chain+Top+25

0 Comments Permalink
0

Intel uses the concept of corporate goals as a way to crystallize what is important across the company.  Every year the CEO and his staff agree on the big items Intel wants to achieve.  These are defined and grading is agreed on.  This is a great recognition tool in that it focuses all needed areas of the company to achieve these goals.

 

From an ERP perspective corporate goals have several advantages.  When running an ERP effort that is one of the corporate goals then it tends to be a lot easier to get support from matrix groups since all groups want to achieve and support the corporate goal.  Generally, groups tend to focus on their own goals (since not all groups have a corporate goal for their activities) but the corporate goals break down cross group barriers and trump group goals.  In years past, ERP in overall or individual programs were not part of the corporate goals.  When this was the case, ERP efforts could be categorized as being IT or business focused.  Items such as ERP upgrades, hardware upgrades, etc. tend to be IT focused.  On the other hand business efforts tend to focus on delivering new functionality (e.g. implement a new Advanced Planning module) that will enable some new element in the business (e.g. a new division or warehouse or improve delivery performance).  When an IT ERP program supports a business corporate goal, then that tends to be a powerful catalyst in terms of ensuring executive and senior management support, resources, and support from other groups.  But the ideal ERP program has both an IT corporate goal and a business corporate goal.  When these rare conditions exist then obstacles are removed as if by magic.  Here the business is extremely motivated as are all the groups needed in IT.  The downside is the amount of visibility and scrutiny tends to be extremely high.  But all in all the positives outweigh the negatives in this “Ideal” ERP scenario. 

 

Whether a corporate goal or not, I would argue that an essential ingredient in ensuring an ERP effort is successful is to ensure both the business and IT think it is a priority.  This may seem obvious but it is not uncommon for an IT department to pursue a major effort that is not necessarily aligned with business priorities.  When this happens, the risk of failure increases dramatically.  At Intel, IT can get a major program included as a corporate goal and this in turn ensures senior business management support.  Although very powerful by itself the effort becomes even more powerful when the same ERP effort is also a business corporate goal.  We have examples of this alignment and it creates a positive environment for ensuring visibility and results.

0 Comments Permalink
0

Everyone wants information security to be easy.  Wouldn’t it be nice if it were simple enough to fit snugly inside a fortune cookie?  Well, although I don’t try to promote such foolish nonsense, I do on occasion pass on readily digestible nuggets to reinforce security principles and get people thinking how security applies to their environment.

 

Common Sense
I think the key to fortune cookie advice is ‘common sense’ in the context of security.  It must be simple, succinct, and make sense to everyone, while conveying important security aspects.

 

Fortune Cookie advice for May:

 

Fear and anxiety will lead to poor risk analysis conclusions

 

Stay focused on the available facts, use a dose of reality to fill in the gaps, and trust reliable risk models to generate analytical conclusions.

 

Excerpt from the Traps of Measuring Security Blog: In our world of information security, we must take a step back from the limitations and biases we possess and stay true to proper forms of analysis in order to see the truth.  It is far too easy for us to slip backwards and inaccurately measure risk of situations we don’t understand.  Let’s continue to remind each other of this fact and challenge risk assessments, especially in situations where concern is more prevalent than fact.

 

So am I contributing to the problem of over simplifying security? Or am I reaching out to those who might not take an inordinate amount of time necessary to understand the complexities and nuances of our industry? You decide and feel free to share your knowledge-nuggets.

 

Fortune Cookie Security Advice - April 2009

Fortune Cookie Security Advice - May 2008

Fortune Cookie Security Advice - June 2008

Fortune Cookie Security Advice - September 2008

Fortune Cookie Security Advice - November 2008

Fortune Cookie Security Advice - August 2008

0 Comments Permalink
1

The challenges for IT when handling an M&A project can be quite daunting to say the least.  But before we go down those winding, twisting roads, I'll start with an overview of the different types of projects we tend to come across related to M&A deals.

M&A refers to mergers and acquisitions.  These are the deals that companies enter into for various business reasons including growing talent quickly, expanding product lines or entering new markets.  For the IT project manager, these types of deals and decisions result in one of several scenarios.

I have yet to be involved in a merger project.  In my mind, a merger is the joining of at least two companies to form a new combined corporate entity.  The original companies would typically be comparable in size and enter into the deal more as partners on somewhat equal footing in terms of control and influence.  Needless to say, the IT challenges of a merger could be enormous.  Again, I haven't had the experience of working on such a project, so I'll certainly spend more time on the other scenarios.

Acquisitions involve, well, the acquisition of a smaller company by a larger company.  Dare I say it, assimilation?  From an IT perspective, this typically involves figuring out how to bring a smaller company's infrastructure and data into the greater corporate IT environment.  I might add that a key challenge of acquisitions is executing this transition without damaging things like culture, process and work efficiency of the acquired company.

Divestitures are the unnamed scenarios of M&A.  Sometimes we talk about M&A&D, which  makes a nice TLA.  :)  A divestiture typically involves the sale of components of one company to another company.  This is different than an acquisition in that only a piece of a company is being acquired by another.  Although one company's divestiture is in fact another company's acquisition.  Interesting, no?

Finally, I must include another scenario which seems to be quite common these days, the site closure.  Although not exactly an M&A style effort, the site closure is often the ultimate end of an acquisition.  Although I am far from an experienced operator when it comes to M&A, I've been around the block enough to see the pattern...big company acquires smaller company...big company extracts value out of acquisition, or not...a few years pass...acquisition site closes.  Of course, I have also seen acquisition sites become key facilities for ongoing operations.  One interesting twist with site closures is that they can sometimes turn into divestitures.  More on that later.

In a nutshell, these are the four major categories of projects we consider within the IT M&A scope.  I will elaborate more on each scenario in future blog posts.  Stay tuned!

I'm curious to know what kinds of M&A projects have impacted IT at your company?

Disclaimer In Plain English:  My efforts are focused on IT systems integration (or the reverse) and I have no involvement with M&A business negotiations or decisions.  I have no knowledge of and cannot comment on or answer questions regarding specific deals, either announced or unannounced.

1 Comments Permalink
0

We naturally take comfort in being able to quantify the vagueness of challenges in our existence.  This past week, I was again reminded the cup of information security is filled partially with the complexities of human perception and ambiguity of emotions weighing our mental models of judgment.  These can be misleading.

 

This is not a revelation.  I thrive in the trenches of security measures and metrics, and learned this lesson many seasons past.  But it is so easy to fall back into the comfort of measuring, calculating, estimating, and even predicting risks with first impressions, and foregoing proper data collection and dispassionate analysis.

 

It is in our very nature to apply our big cognitive brains in an attempt to make sense of something which causes concern for our minds when we encounter situations we fail to grapple.  We default to familiar structures of logic and experience to give some insight, even if it is invalid.  If we cannot grasp a cloud, it makes us feel better to at least measure it.

 

I recently travelled to the beautiful city of Shanghai.  In the sprawling city of 19 million, getting about requires the use of a local taxi.  Drivers are aggressive by American standards.  They creatively use all lanes, including those of oncoming traffic, to weave in and out between pedestrians, other vehicles, and bicycles, all at high speed.  Roadway guides such as speed signs, stoplights, and lane markers are just cosmetic.  The concept of ‘right of way’ is defined by the vehicle which gets there first.  Tens of thousands of taxi drivers vie for pole positions at every light and traffic snarl.  I counted no less than half a dozen head-on near misses the first day.

 

Not surprisingly I was a bit concerned for my safety.  But what was the actual risk?  It seemed high, with all the jockeying, speed challenges, and lurching in front of other cars at a moment’s notice.  In formal terms, the security risk calculation was off the map.  Keeping it simple, risk can be defined as equaling the (threat) x (consequence) x (vulnerability).  Threats were abundant and vectoring from every angle.  Vulnerabilities were painfully obvious as the situation was an example of near uncontrolled chaos heavily dependent upon human judgment and intervention.  Lastly, the consequences registered as likely life threatening.  Vehicle safety measures are not equal to US standards, with no airbags and rarely a functioning seatbelt.  My brain began to do the rough math and formed a mental model where the conclusion was somewhere near the “I’m screwed” end of the spectrum.

 

Over time, I started to take a different perspective.  By the end of the week, and too many close calls to count, I observed the city’s taxi’s did not show damage which would be consistent with rampant numbers of collisions.  Although chaotic and unpredictable, they found a balance in avoiding impacts.  My drivers’ never appeared nervous.  Many were happy to take calls on their cell phones while racing into oncoming traffic and weaving back into our directional flow at the last second.  Yet, they were not worried.  The pedestrians who seemed intent on walking into direct paths of vehicles always looked up at the last possible moment and jumped out of the way of an untimely demise.

 

The dangers were still there.  Nothing changed but my perception.  The risks were high, controls were low, but it was the incident rate that was the telling measure.  Lack of vehicle accidents in such a tremendous population meant they operated in an efficient manner which my brain could not comprehend as safe.  But it was.  My initial evaluation misled me to a wrong conclusion: an inaccurate determination of risk.  I felt safer than before.  To this day, I cannot comprehend how they do it.

 

In our world of information security, we must take a step back from the limitations and biases we possess and stay true to proper forms of analysis in order to see the truth.  It is far too easy for us to slip backwards and inaccurately measure risk of situations we don’t understand.  Let’s continue to remind each other of this fact and challenge risk assessments, especially in situations where concern is more prevalent than fact.

0 Comments Permalink
0

Everyone wants information security to be easy.  Wouldn’t it be nice if it were simple enough to fit snugly inside a fortune cookie?  Well, although I don’t try to promote such foolish nonsense, I do on occasion pass on readily digestible nuggets to reinforce security principles and get people thinking how security applies to their environment.

 

Common Sense
I think the key to fortune cookie advice is ‘common sense’ in the context of security.  It must be simple, succinct, and make sense to everyone, while conveying important security aspects.

 

Fortune Cookie advice for April:

 

Capability, intent, and focus are the defining aspects to quickly prioritize threats.


The world of information security threats is vast.  We can easily be overwhelmed with different components, processes, impacts, and concerns.  Quickly identifying the benign from the urgent is a competitive advantage.  In order to organize and prioritize, we must have a consistent method to judge criteria.

 

I submit the three most compelling aspects are related to the attacker who is committing the violation.  Their capability to do harm, defines the likelihood of a successful attack.  The intent of the attacker has significant implications for the likelihood to detect activity and the persistence of continuing attempts.  Lastly, the focus of the attack, whether it is targeting you specifically or just looking for opportunistic victims, completes the overlapping picture to understand the precision of activities.

 

Given these three aspects, a quick evaluation can be made to determine the severity of the threat and attacks.  Of course this is just the first step necessary for triage, while a full evaluation should be conducted for the areas which rise to the top of the severity list.

 

Fortune Cookie Security Advice - May 2008

Fortune Cookie Security Advice - June 2008

Fortune Cookie Security Advice - August 2008

Fortune Cookie Security Advice - September 2008

Fortune Cookie Security Advice - November 2008

Fortune Cookie Security Advice - December 2008

Fortune Cookie Security Advice - January 2009

Fortune Cookie Security Advice - February 2009

Fortune Cookie Security Advice - March 2009

0 Comments Permalink
1

ERP?

Posted by Soren Andersen May 1, 2009

ERP stands for Enterprise Resource Planning.  The term evolved from earlier terms such as Material Requirements Planning (MRP, sometimes referred to as little MRP to distinguish it from Manufacturing Resource Planning) and Manufacturing Resource Planning (sometimes referred to as big MRP or more generally MRPII).  Material Requirements Planning focused on time phased planning of materials required in support of manufactured items (based on a Bill of Material).  These could be finished products or components.  It ensures the right materials are at the right place at the right time in the appropriate quantity.  The techniques associated with MRP became feasible during the 1960's as computers became more available to businesses.  This approach enabled reductions in inventory while at the same time improving customer service, which had been thought unlikely with older inventory control theories.  Manufacturing Resource Planning, the next evoloution of MRP, kept Materials Requirements Planning and added to it, by including financials and marketing.  MRPII provided the coordination between production, finance, and marketing.  The idea was to create a closed loop system between these three key areas of a manufacturing enterprise.  With ERP the definition was further expanded to include additional business domains and also to support businesses/enterprises beyond just manufacturing companies.  MRP, MRPII, and ERP are a combination of both business process theory and the software application suites that enable these processes.  Today’s major ERP packages generally support finance, human resources, procurement, product development, sales and marketing, manufacturing and supply chain management.  This is not all inclusive as vendors have tended to extend their footprint to all areas of the enterprise.  Generally, application vendors aim to create integrated applications across these domains and provide a single database for one version of the truth, so to speak.  The other thing that is generally claimed is that the applications contain best practices which will help drive operational improvements as a result of implementing.

 

Intel started its ERP implementation effort over a decade ago.  As most large corporations, Intel has implemented elements of ERP throughout the company across this timeframe.  We did not implement all elements at once or at all our business groups.  Programs/projects were planned and launched based on business need, ROI, and business readiness.  Being an engineering and manufacturing company Intel has been able to leverage the original concepts of MRP/MRPII and the newer elements of ERP.  Moving forward I plan to relate some of my experiences and general thoughts on the ERP efforts I have been involved with here at Intel.

1 Comments Permalink
1

My name is Soren Andersen.  I work in Intel’s Information Technology Supply Network Capability group as a manager delivering strategic Enterprise Resource Planning (ERP) programs and projects.  My goal is to blog about the challenges of delivering ERP in a large corporation such as Intel.  My intent is to focus on delivering ERP to enable the business.  Since I am from Intel you might expect me to blog about Intel products.  However, I will leave that to other company experts.  In this entry I will provide you some background on who I am and also provide some context and a framework for upcoming entries.

 

I have worked in the Information Technology/Information Systems field for over 20 years.  My degree is in Industrial Engineering.  The first 6 plus years I spent at Electronic Data Systems (EDS, which is now a part of Hewlett Packard) conducting systems integration on engineering and manufacturing systems in the Midwest.  I spent the latter part of my time there as a manager delivering imaging systems for government, manufacturing, and medical industries.  The environment was mainframe, Unix, and then PCs leading to client/server systems.  Next, with a move into a start up consulting firm I worked in the manufacturing/supply chain systems arena primarily for manufacturing high tech clients in the Pacific Northwest.  Here the focus was on both custom client/server applications and packaged software focused on advanced planning for supply chain.

 

After 11 plus years at Intel I have had the opportunity to work in a variety of roles in IT/IS environments.  Most of these focused on delivering Enterprise Resource Planning (ERP) systems.  I have worked on the strategic front end defining roadmaps and budget to implement ERP.  I have delivered multiple large ERP components to various divisions within Intel.  And have had the opportunity to run a consolidated ERP support organization of up to 175 people worldwide.  I have also had the opportunity to work on multiple efforts such as B2B (Rosettanet, Web, etc), Reporting/Business Intelligence/Analytics, etc which tend to be at the periphery of ERP efforts but at the end of the day are also critical to their success.  In all of these roles the common denominator has been that I have always been a people manager while at times also carrying the program manager title.  I mention this since this is my vantage point.  There are those who are strictly people/resource managers and their focus is on developing people and there are those who are individual contributor program managers who focus strictly on the programs and leverage matrixed resources.  I have managed teams where all resources down to the analysts and the programmers reported to me and then, as I am doing now, have managed product managers, program managers, project managers, technical leads, and architects without the bulk of the resources.  But I think what permeates my perspective is the fact that I am a manager with responsibility for a team that is responsible for delivering key ERP programs.

 

In terms of what you can expect from me with these blogs, here are some of the topics that I work with, come across, and interest me:  Program/Project Management, Resource Management, Program Management Office (PMO), Roadmaps, yearly Budgeting, Steering Committees/Management Review Committees, Roadmaps, Methodologies for ERP (e.g. Agile, Waterfall, etc), Processes (e.g. Program Lifecycle, CMMi, etc), Value of programs, metrics, teams (geo dispersed, large vs small, in-house/outsourced/contract), Supply Chain, and whatever else I may be working with in the course of delivering ERP solutions at Intel.  I welcome your inputs for additional topics as well.  I am looking forward to not just sharing my own thoughts but also learning from fellow travelers in the field of delivering ERP.

1 Comments Permalink
0

First, Happy Earth Day Everyone!

 

A couple of weeks ago, I told you about a small proof of concept we conducting to measure energy use in the office environment and to then use that established baseline to test different energy saving methods. This PoC is currently in a planning stage, but we hope to start physical metering within the next few weeks. Stay turned for more info.

 

Today, I’d like to quickly tell you about a little effort to increase awareness of energy use in the office. Often, we have little to no understanding of how much energy we are using, nor how much it is costing us. Awareness can positively influence behavior and reduce energy use. Several studies of energy use in the home have show awareness of real time whole house energy use resulted in the voluntary reduction of use by 10%-15%. To help increase awareness internally, IT measured the energy use of several items found in a typical office such as, desktops, laptops, LCD displays, and phone and headset chargers. This information will soon be published internally via a simple web page showing a photo of a typical office space. As the viewer moves their mouse over each device in the office, a pop-up will show how much energy that device uses in various states. Below the photo is a general summary of how much energy and money could be saved if various generalized behaviors were changed. Lastly, there is a link to more details. It’s very simple, but should greatly help increase awareness of energy use in the office.

 

How about you? Are you doing anything to help increase awareness of energy use in your office spaces? Would something like this work for you?

 

-Mike

0 Comments Permalink
3

Is the value of patch management decreasing?  Some experts say, due to a rise in privately held vulnerabilities, the value of patch management is eroding.  Others feel patching is losing the race and becoming too little and too late with the rapid development of attackers.  I too have chimed in on the topic and stated patching all vulnerabilities is not economical, as most are never widely exploited.  But does this mean we should be looking at alternate paths, away from patch management?  I stand firm in support of the end-node update concept, but take a slightly different view of the scope and value.

 

I see ‘patch management’ as the strategic capability of managing end nodes.  I consider the delivery of ‘patches’ as a broad term which includes OS, application, and hardware BIOS upgrades which can benefit the security posture of the device.  This includes and is akin to the widely accepted delivery of security product updates for anti-virus, anti-spyware, firewalls, etc.  Some of which are updated daily.

 

Attacks are constantly changing.  They normally take advantage of poor coding practices, use design functionality in unintended ways, or exploit avenues to misguided end-user judgment.  The ability to update systems is crucial to maintain security equilibrium.  It is a support function for systems to adapt to new threats.  This capability has a multitude of benefits, both strategic and tactical.  Being able to reach out to systems allows for a better understanding of the number, type, and usage of systems in the environment.  An effective system can paint a picture of systems at risk.  It is a sweeping means to close identified vulnerabilities in deployed code, which can reduce the exposure surface.  It can be used to respond to compromises and drive clean-up activities.  Such services can raise the general security level of a community and may drive to a more homogenous security stance, which strongly lends towards efficiency.

 

Mapping ‘patch management’ against a defense-in-depth model shows it allows for Prevention of exposure to known vulnerabilities where patches exist.  It can provide Detection capabilities to improve alerting of attempted as well as successful attacks.  Once systems are compromised, this Response function aids in the restoration of services back to a norm state.  The combination of indicators generated in these areas may assist in efficiency improvements and be used to comprehend future trends, therefore providing a potential Prediction opportunity

 

Overall, actively managing end-node security via ‘patch management’ is very important.  I doubt any serious security professional is advocating turning off all patch or remote system security updates.  The value may vary over time and across different systems, but we have a lot of control in how this capability evolves and the value it returns.  We are empowered to maximize the return on investment.

 

The question still remains, from a measures and metrics perspective, how best can we show and quantify the benefits, efficiency, and value.  The industry as a whole has yet been able to adequately or consistently tackle this challenge.  That discussion is fodder for another blog.

3 Comments Permalink
1 2 3 ... 10 Previous Next