OASIS Open Repositories: Individual Contributor License Agreements

The following public record of signed Individual Contributor License Agreements governing the OASIS Open Repositories reflects the current status of Individual CLAs.

An active Individual CLA is required for a Pull Request to be honored in any OASIS Open Repository.

Optional Entity Contributor License Agreements may be submitted by an entity to record their support for their employees’ contributions. Record of Entity CLAs can be found at https://www.oasis-open.org/resources/open-repositories/cla/view-entity.

Filter

Contributor Name: Stephen Thomson

Contributor Email: sthomson@caci.co.uk
Github Username: StephenThomson
Employer Name: CACI
Employer Contact Email: info@caci.co.uk
Begin Date: 2017-06-08T15:14:43+00:00
End Date:

Contributor Name: Yumna Ghazi

Contributor Email: yumnaghazi@gmail.com
Github Username: yghazi
Employer Name:
Employer Contact Email:
Begin Date: 2017-05-19T17:11:00+00:00
End Date:

Contributor Name: Andras Iklody

Contributor Email: andras@circl.lu
Github Username: iglocska
Employer Name:
Employer Contact Email:
Begin Date: 2017-05-05T12:45:46+00:00
End Date:

Contributor Name: Raphaël Vinot

Contributor Email: raphael.vinot@circl.lu
Github Username: rafiot
Employer Name:
Employer Contact Email:
Begin Date: 2017-05-05T12:45:29+00:00
End Date:

Contributor Name: Alexandre Dulaunoy

Contributor Email: alexandre.dulaunoy@circl.lu
Github Username: adulau
Employer Name:
Employer Contact Email:
Begin Date: 2017-05-05T12:43:12+00:00
End Date:

Contributor Name: Lewis John McGibbney

Contributor Email: lewis.mcgibbney@gmail.com
Github Username: lewismc
Employer Name:
Employer Contact Email:
Begin Date: 2017-04-09T15:55:06+00:00
End Date:

Contributor Name: Omer

Contributor Email: omer.dashti@ecitele.com
Github Username: omer-d
Employer Name:
Employer Contact Email:
Begin Date: 2017-04-06T07:51:46+00:00
End Date:

Contributor Name: Stefan Hagen

Contributor Email: stefan@dilettant.eu
Github Username: sdrees
Employer Name:
Employer Contact Email:
Begin Date: 2017-02-15T17:19:12+00:00
End Date:

Contributor Name: Robert N. Thomas

Contributor Email: bob.thomas@tagsmiths.com
Github Username: robertnthomas
Employer Name:
Employer Contact Email:
Begin Date: 2017-01-03T19:48:14+00:00
End Date:

Contributor Name: Sijia Chen

Contributor Email: sijia1996@gmail.com
Github Username: cjschen
Employer Name: Caren Morrison
Employer Contact Email: caren.morrison@rbc.com
Begin Date: 2016-12-19T15:48:11+00:00
End Date:

Contributor Name: Jeremie Boudreau

Contributor Email: JeremieABoudreau@gmail.com
Github Username: JeremieBou
Employer Name: RBC
Employer Contact Email: caren.morrison@rbc.com
Begin Date: 2016-12-19T15:46:54+00:00
End Date:

Contributor Name: Tim Grantham

Contributor Email: tgrantham@timgrantham.com
Github Username: tgrantham
Employer Name:
Employer Contact Email:
Begin Date: 2016-10-28T13:32:41+00:00
End Date:

Contributor Name: Kevin Mangold

Contributor Email: kevin.mangold@nist.gov
Github Username: kevinmnagold
Employer Name: National Institute of Standards and Technology
Employer Contact Email: kevin.mangold@nist.gov
Begin Date: 2016-10-21T18:09:40+00:00
End Date:

Contributor Name: Jacques Durand

Contributor Email: jdurand@us.fujitsu.com
Github Username: jdanrud
Employer Name: Fujitsu North America
Employer Contact Email: AZmyslowski@us.fujitsu.com
Begin Date: 2016-10-20T16:48:53+00:00
End Date:

Contributor Name: Chris Lauwers

Contributor Email: lauwers@ubicity.com
Github Username: lauwers
Employer Name:
Employer Contact Email:
Begin Date: 2016-10-20T16:32:26+00:00
End Date:

Contributor Name: Terry MacDonald

Contributor Email: terry.macdonald@cosive.com
Github Username: terrymacdonald
Employer Name: Cosive
Employer Contact Email: terry.macdonald@cosive.com
Begin Date: 2016-09-18T00:29:20+00:00
End Date:

Contributor Name: Jennifer Burns

Contributor Email: jburns@mitre.org
Github Username: jburns12
Employer Name: MITRE
Employer Contact Email: gback@mitre.org
Begin Date: 2016-09-16T17:38:35+00:00
End Date:

Contributor Name: Ivan Kirillov

Contributor Email: ikirillov@mitre.org
Github Username: ikiril01
Employer Name: MITRE
Employer Contact Email: hssedi_info@mitre.org
Begin Date: 2016-09-15T15:48:41+00:00
End Date:

Contributor Name: Emmanuelle Vargas-Gonzalez

Contributor Email: emmanuelle@mitre.org
Github Username: emmanvg
Employer Name: MITRE Corporation
Employer Contact Email: emmanuelle@mitre.org
Begin Date: 2016-09-15T15:17:33+00:00
End Date:

Contributor Name: John Wunder

Contributor Email: jwunder@mitre.org
Github Username: johnwunder
Employer Name: MITRE
Employer Contact Email: jwunder@mitre.org
Begin Date: 2016-09-14T15:32:14+00:00
End Date:

Contributor Name: Jon Baker

Contributor Email: bakerj@mitre.org
Github Username: jonathanbaker
Employer Name:
Employer Contact Email:
Begin Date: 2016-09-13T14:54:37+00:00
End Date:

Contributor Name: Alex Tweed

Contributor Email: atweed@mitre.org
Github Username: atweedMITRE
Employer Name:
Employer Contact Email:
Begin Date: 2016-09-13T12:15:34+00:00
End Date:

Contributor Name: Aukjan van Belkum

Contributor Email: aukjan@vanbelkum.nl
Github Username: aukjan
Employer Name: EclecticIQ B.V.
Employer Contact Email: info@eclecticiq.com
Begin Date: 2016-09-13T09:24:28+00:00
End Date:

Contributor Name: Vernon Olin "Trey" Darley, III

Contributor Email: trey@kingfisherops.com
Github Username: treyka
Employer Name:
Employer Contact Email:
Begin Date: 2016-09-13T08:33:51+00:00
End Date:

Contributor Name: Michael Chisholm

Contributor Email: chisholm@mitre.org
Github Username: chisholm
Employer Name:
Employer Contact Email:
Begin Date: 2016-09-12T21:55:32+00:00
End Date:

Contributor Name: Michael Kouremetis

Contributor Email: mkouremetis@mitre.org
Github Username: mbastian1135
Employer Name:
Employer Contact Email:
Begin Date: 2016-09-12T19:23:48+00:00
End Date:

Contributor Name: Patrick Maroney

Contributor Email: pmaroney@specere.org
Github Username: packet-rat
Employer Name: Integrated Networking Technologies, Inc.
Employer Contact Email: pmaroney@specere.org
Begin Date: 2016-09-12T19:09:31+00:00
End Date:

Contributor Name: Richard Piazza

Contributor Email: rpiazza@mitre.org
Github Username: rpiazza
Employer Name:
Employer Contact Email:
Begin Date: 2016-09-12T18:49:00+00:00
End Date:

Contributor Name: Chris Lenk

Contributor Email: chris.lenk@email.com
Github Username: clenk
Employer Name:
Employer Contact Email:
Begin Date: 2016-09-09T11:56:17+00:00
End Date:

Contributor Name: Greg Back

Contributor Email: gtback@gmail.com
Github Username: gtback
Employer Name:
Employer Contact Email:
Begin Date: 2016-09-01T17:52:04+00:00
End Date:

Contributor Name: Matt Rutkowski

Contributor Email: mrutkows@us.ibm.com
Github Username: mrutkows
Employer Name:
Employer Contact Email:
Begin Date: 2016-08-25T16:27:35+00:00
End Date:

Contributor Name: Luc Boutier

Contributor Email: luc.boutier@fastconnect.fr
Github Username: lucboutier
Employer Name:
Employer Contact Email:
Begin Date: 2016-08-23T07:21:39+00:00
End Date:

Contributor Name: Grant Vergottini

Contributor Email: grant.vergottini@gmail.com
Github Username: grantcv1
Employer Name: Xcential Corporation
Employer Contact Email: info@xcential.com
Begin Date: 2016-06-09T18:36:41+00:00
End Date:

Contributor Name: Véronique Parisse

Contributor Email: V.PARISSE@aubay.lu
Github Username: vparisse
Employer Name:
Employer Contact Email:
Begin Date: 2016-06-06T12:06:01+00:00
End Date:

Contributor Name: Fabio Vitali

Contributor Email: fabio@cs.unibo.it
Github Username: fvitali
Employer Name:
Employer Contact Email:
Begin Date: 2016-06-03T12:49:37+00:00
End Date:

Contributor Name: Monica Palmirani

Contributor Email: monica.palmirani@unibo.it
Github Username: https://github.com/palmirani
Employer Name: University of Bologna, CIRSFID
Employer Contact Email: monica.palmirani@unibo.it
Begin Date: 2016-06-03T12:14:07+00:00
End Date:

Contributor Name: Mark Giffin

Contributor Email: mark@markgiffin.com
Github Username: markgif
Employer Name:
Employer Contact Email:
Begin Date: 2016-03-31T21:40:13+00:00
End Date:

Contributor Name: Carlos Evia

Contributor Email: cevia@vt.edu
Github Username: carlosevia
Employer Name: Virginia Tech
Employer Contact Email: eska@vt.edu
Begin Date: 2016-03-28T20:33:43+00:00
End Date:

Contributor Name: Don R. Day

Contributor Email: donday@learningbywrote.com
Github Username: donrday
Employer Name:
Employer Contact Email:
Begin Date: 2016-03-28T15:53:04+00:00
End Date:

Contributor Name: William Eliot Kimber

Contributor Email: ekimber@contrext.com
Github Username: drmacro
Employer Name:
Employer Contact Email:
Begin Date: 2016-03-23T15:04:54+00:00
End Date:

Testimonials

Cybersecurity is one of the greatest challenges our modern society faces and requires a coordinated approach to succeed. Under OASIS leadership, we see an opportunity to better organize the good guys to fight cybercriminals by sharing cyber threat intelligence data in an automated and efficient data standard.

Peter Allor

Senior Security Strategist

IBM

OASIS TC members act like extra QA resources for one another. We put our products together and shake out incompatibility issues. Finding those before we ship is invaluable.

Jay Brown

Senior Software Engineer

IBM

One thing that makes OASIS stand out is its openness. It’s not just that the standards are open and freely available in perpetuity, but also that the whole process is open.

Peter Brown

Independent Consultant

As a Sponsor of the OASIS CTI Technical Committee, we are delighted to be at the forefront of advancing critically important standards like STIX, TAXII and CybOX. By creating protocols that address how to best model, analyze, and share cyber threat intelligence, we can provide greater support to overwhelmed security professionals.

John Bruce

Chairman and CEO

Resilient Systems

Soltra is proud to be a member of the OASIS CTI Technical Committee. Our threat information sharing solution, Soltra Edge, was built leveraging STIX, TAXII, and Cybox – key standards within the industry. We look forward to contributing to CTI as we continue to establish and maintain open standards, while improving cyber security capabilities and reducing workload.

Aharon Chernin

CTO

Soltra, a DTCC and FS-ISAC Company

Open standards and community sharing are vital components of a successful and effective fight against cybercrime. Our goal is to make Threat Intelligence, from a variety of sources, timely and actionable.

Dorit Dor

VP, Products

Check Point

Focusing on standardizing threat intelligence technologies to keep sensitive government and corporate information secure is paramount to the mission of OASIS and its members. At ViaSat, we take a comprehensive approach to cybersecurity, from identifying potential cyber and physical security vulnerabilities to designing and implementing a plan that leverages big data analytics, intuitive visualization and intelligent automation to keep pace with evolving threats no matter where data resides on the network or how it is accessed.

Jerry Goodwin

VP, Secure Network Systems

ViaSat

iSIGHT Partners, creator of the commercial cyber threat intelligence category, understands how security organizations can gain the advantage over adversaries by using threat intelligence across their security and risk management program. As an early contributor and enabler of STIX, we welcome the opportunity to join with OASIS to further develop CTI standards and accelerate the adoption of context rich threat intelligence.

Robert Huber

VP Community

iSight Partners

At OASIS, you don't have to be a large vendor to influence work. Of all the standards bodies we’ve participated in, OASIS is the only one we recommend with no hesitation. It is a group that simply works.

Tim Hudson

Technical Director

Cryptsoft Pty Ltd

We are proud to support the work OASIS is doing to advance their cybersecurity specifications and promote information sharing, a critical factor in today's security posture. By sharing details about malicious incidents quickly, not only between the public and private sectors, but across industry lines within the private sector as well, we can work together to better defend ourselves and stay ahead of the hackers.

Paul Kurtz

Founder and CEO

TruSTAR Technology

STIX and TAXII in particular are important initiatives towards next generation threat intelligence. Using the same terms, data streams, and threat modeling methods will help researchers, vendors, and law enforcement alike share information back and forth to stay abreast or even ahead of threat actor groups. We are pleased to contribute to this and more through OASIS.

Derek Manky

Global Security Strategist

Fortinet

We have long been committed to any advances that can better enable the sharing of threat intelligence among security professionals. Until now, organizations have been hampered by a lack of common standards and the tendency for security information to be siloed. We strongly support this important endeavor and look forward to contributing to the standardization being led by OASIS.

Paul Martini

CEO and Co-founder

iboss Cybersecurity

NEC is very pleased to be part of the CTI Technical Committee and continues to drive CTI adoption with industry partnerships to benefit customers. NEC believes that threat intelligence standards are crucial for proactively countering the cyber threat. We are excited about the formation of CTI TC and support its efforts through its contributing to and promotion of this global standard.

Kozo Matsuo

General Manager, Cyber Security Strategy Division

NEC Corporation

We have been advocates of STIX, TAXII and CybOx for some time. OASIS as an international standards checkpoint will undoubtedly improve threat intelligence sharing amongst partners by facilitating the exchange of computer-readable threat information.

David Maxwell

Director of Threat Intelligence

eSentire

OASIS strikes the right balance between the amount of structure you need for real standards and the amount of flexibility you need for cutting-edge innovation.

Drummond Reed

XDI.org

Development of an industry-wide standards framework for cyber threat intelligence is crucial for the information security industry to be able to define and share threats. New Context is a proud sponsor of OASIS and believes strongly in open and transparent standards frameworks development. We look forward to collaborating on the next standards for STIX, CybOX and TAXII.

Daniel Riedel

CEO

New Context

I always encourage vendors with products related to access control, security, or cloud computing to join the appropriate OASIS Technical Committees and contribute to the standards work. We all benefit that way.

John Tolbert

VP, Cybersecurity

Queralt

OASIS provides an auditable, transparent and justifiable process. It makes it easy for anyone to understand how the CAP-AU Profile was developed.

Greg Trott

CAP-AU Project Manager

Australia Attorney-General's Dept

OASIS members continue to amaze me by their deep knowledge of technology. I can ask a question on a TC call and get more valuable feedback in minutes than I would from spending days in a conference.

Pim van der Eijk

Owner

Sonnenglanz Consulting

OASIS gives me access to very high-level colleagues. Every TC meeting is like an intensive research seminar on a topic in our field.

Adam Wyner, Dr.

Research Associate

University of Liverpool

OASIS Open Repositories: Individual Contributor License Agreements

Connect with OASIS

Testimonials

Other sites: