Category

Security News

Untitled-4

7 Things to Consider in 2016 Security Testing Plans

By | Security News | No Comments

21stca-7f93936d-31ba-4d7d-b255-826a6b060f12-v2
As you consider  security testing plans for 2016, we want to provide guidance based on what we are seeing from security testing clients so far this year.  Risk assessments and security testing are an important part of any information security program but in an environment were budgets are constrained we need to spend security testing dollars wisely.  Here are seven things to consider when making your 2016 security testing plans.

Read More

Remove Vulnerabilities to Improve Company Security

By | Security News | No Comments

Removing vulnerabilities is crucial to managing your information security risks.

We can help lower an organization’s ongoing security risk by lowering the vulnerabilities or weaknesses in computer software and operating systems. This reduces weaknesses available for exploit by a cybercriminal or malware or other threat.

Leave the keys in the car with the door unlocked and sooner or later the car is going to be stolen.

Leave the infrastructure and applications that run the business unpatched and sooner or later something bad is going to happen.

Vulnerability management (or VM for those of you who insist on communicating with acronyms) a repeatable process or practice of identifying vulnerabilities (especially for software and firmware) within the enterprise, classifying them by their severity and either remediating or accepting the risk they pose to the environment. A vulnerability management process steps through identifying, classifying, remediating and mitigating vulnerabilities, or weaknesses, in software applications and operating systems.

Vulnerability management is a critical leading security practice for an organization of any size. It is an expectation to meet compliance with the Payment Card Industry’s Data Security Standard and other regulatory authorities.

Many of the steps or processes involved in VM use technology to automate some of the work.

Jacadis uses QualysGuard in the field as well as with customers building their own vulnerability management program. With Qualys we can map a network to identify the systems that are on it. We can then scan each system and identify vulnerabilities on that system. Qualys ranks vulnerabilities by severity. We can then prioritize fixing them by severity. Qualys provides support for the workflow of getting found vulnerabilities fixed and confirming that the fix has been successful.

Some clients are overwhelmed with vulnerability data and find they need consider threats as a part of their vulnerability prioritization. In those environments Jacadis uses Kenna’s product to integrate the results of vulnerability scan data with the results from 8 different threat feeds. This accelerates the prioritization of what needs fixed first in order to improve the company’s security posture.

Tools are important, but it isn’t as simple as just scanning and fixing.

Once scanned there are other steps that need IT staff involvement. Patches need to be deployed, applications updated and systems hardened. Sometimes exceptions need to be managed. Other times countermeasures need to be implemented because not all vulnerabilities can simply be fixed with a patch.

And the process isn’t a one-time thing. It needs to be implemented as a routine regular recurring mature process.

We believe there are five core components to a mature vulnerability management program:

  1. Vulnerability Management Policy, which defines the organization’s vulnerability management posture, the level of security the firm wants to maintain, key processes within the firm’s vulnerability practices, reporting and compliance. The policy guides IT staff in performing the function and guides management in providing oversight.
  2. Patch Management Policy, which defines the organization’s stance on patching including the frequency of patching, testing, deployment, auditing, recovering from flawed patches, reporting and compliance.
  3. Automated vulnerability scanning tools are necessary in today’s environment as both a security leading practice and oftentimes as a compliance requirement.
  4. Reporting and metrics requirements should be defined in both the Vulnerability Management and the Patch Management Policy. Many of our clients regularly report vulnerability and patch management efforts to their information security steering committee for oversight.
  5. Audit and compliance requirements should be defined in both the Vulnerability Management Policy and the Patch Management Policy. Staff and tools need to be deployed to verify that the practices defined in the policies are being followed.

 

 

 

Risk Management: An Information Security Trend that Matters

By | Security News | No Comments

Learning how to use Risk Assessments and ongoing Risk Management tools is going to be crucial to companies building information risk management programs in 2016.

As one year ends and another begins it is a sure bet that tech company marketing teams will begin to crank out the trend reports.  The transition this New Year is no different.

The cynic recognizes the pattern.  This company identifies these threats that only their product protects against.  That company identifies another set of threats that only they, of course, protect against.  And so it goes.

Not all of these surveys are bad.  Some are quite helpful in keeping informed about the security landscape.  But they are all put out with the intent of creating demand for products.

We have been doing this long enough that we realize it isn’t about the products.

The trend we see going into 2016 is that companies need to get better at understanding their individual risk profile and building the discipline to manage risk within that profile.  Security safeguards – including products purchased – should be selected based on the risks that they mitigate.

What is risk?

The same joke gets told in security industry conferences all the time. If you put five risk professionals in a room and ask for a definition of risk, you’ll get at least six models.

The “industry” doesn’t agree all the time on the details of the risk model.  But your job isn’t to argue about the fine details of a model. Your job is to manage risk so your organization can run and grow.

Simply – and there is agreement here — risk is the product of the likelihood of something bad happening times the impact that occurs if it does happen (Risk = Likelihood x Impact).

We appreciate and usually use a simple model with a little more detail.

Jacadis uses the definition of risk outlined in NIST 800-30 which is represented mathematically as Risk = Asset x Threat x Vulnerability x Likelihood x Impact where the variables are defined as follows:

Assets in this context are your information and data valuables from your computers, other form factors, servers, network devices and networks to the applications and databases that contain them to the physical locations they are housed to the processes employed to use them for productive work to, of course, the people that use them.

Threats are the bad guys, the bad actors, the malicious code or the act of God that can impact the confidentiality, integrity and/or availability of information and data contained in your assets.

Vulnerability are the chinks in your armor, missing patches, poor practices, weak passwords or other weaknesses that allow a threat to launch an attack on an asset.

Without the jargon your valuables (assets) are attacked by bad actors (threats) through the exploitation of weaknesses (vulnerabilities).

What do we defend first?  Where do we start when we have more assets, threats and vulnerabilities than we can manage?   We need a means of prioritizing the risk.

In the model we’ve chosen, we use Likelihood and Impact represented on a qualitative scale with 1 being low likelihood or low impact and 5 representing high likelihood or high impact.  There are models that used detailed quantitative measures but our experience is that the qualitative, with some limitations, gets us to a point where we can prioritize the cataloged risk and get an organization started on the way to improving its information risk management program and its security posture.

Risk Assessment V. Risk Management

Jacadis conducts a large number of risk assessments annually.  An annual risk assessment (sometimes coupled with security controls assessments and penetration tests) is considered a leading security practice.

A risk assessment focuses on identifying, measuring and prioritizing risks.  Sometimes a risk assessment focuses on an entire organization, sometimes a single system.  Focused on the scope of the assessment, we will report back to the client on risks identified.  We will quantify them and using qualitative scores for likelihood and impact help the client prioritize them.  Finally, we will include a risk treatment plan of recommendations to what needs to be done to reduce the found risks.  Broadly our recommendations will be to:

  • Accept the risk
  • Avoid the risk
  • Mitigate or control the risk
  • Transfer the risk

While the risk assessment is a one-time event or snapshot of the risks found in an analysis of the in scope systems, risk management is an ongoing process.

We like to see clients create a risk register to maintain a catalog of risks that is used as the center point of the risk management process.

Many clients take our initial baseline assessment with the findings and risk treatment plan in spreadsheet format and use that to create the foundation of their risk register.

Others choose to do this in a GRC tool like what our partner TraceCSO provides.

Regardless of your chosen tools, the risk register is important to the risk management process.  It is a tool that will help management understand the risks the organization faces, understand the risks or likely impacts, serve as a basis to communicate about the organization’s risk tolerance and its willingness to accept risk and finally report the status of found risk over time.  It is also a great capture point for technical and non-technical managers to park those things that “keep them up at night” so they are available for discussions during security committee meetings.

Like a risk assessment our client use the risk register to support risk management in across four phases:

  1. Identify the risk in terms of asset, potential threats and identified vulnerabilities.
  2. Evaluate the severity of the risk by calculating using qualitative choices for likelihood and impact
  3. Identifying possible solutions and communicating the potential reduced risk from each choice
  4. Monitoring and analyzing the implementation of solutions; and,
  5. Memorializing your company’s information risk management effort in the case of a breach or audit event.

In that regard, Jacadis is a continuous risk management company.  We help our clients identify risks, evaluate the severity, identify and select countermeasures to and monitor and analyze the effectiveness of the steps taken.  We help them do it through risk assessments and through teaching them how to use a risk register, either in spreadsheet form or as part of a GRC toolset like what TraceCSO provides, as the core of their information security program.

Continuous Risk Management means continuous improvement of security and compliance.

Overwatch: Staying on Top of Your Vulnerabilities

By | Security News | No Comments

If you’re an information security professional, you know that managing your vulnerabilities in your environment isn’t a sprint. It’s a marathon.

New vulnerabilities are discovered each day, and it isn’t enough for us to turn on Windows Updates and hope for the best. Attackers aren’t just looking at OS vulnerabilities. They’re also looking at the software you have on your desktop, that nifty app on your mobile phone, and the scripts you have running on your website.

Read More