GuidesAPIsCommunity

The New FireEye Developer Hub!

It doesn't matter if it's your first time writing code, if you're a researcher, or if you're writing enterprise software—whether you call yourself a developer, engineer, coder, or scripter, this hub will be for you! Soon you will be able to find anything that you need to write code while working with FireEye. While we work on getting the new Developer Hub built, here are just a few scenarios in which you might find our Developer Hub useful:

You are:

  • An enterprise developer looking to integrate with our products
  • A SOC analyst looking to improve their workflow with FireEye products
  • A security researcher interested in taking part in our bug bounty program
  • A customer looking for a deeper integration with FireEye products
  • A technical partner looking to integrate FireEye into your ecosystem

What Can You Expect To Do Here?

The new hub will provide a few major sections: Community, SDKs & Tools, and Content (docs, videos, blog posts, etc.). We already have a community in place for you today as well as the start of some new docs and more will be coming soon. Read the sections below to get a sense of what they can do for you!

Community

We built the FireEye Developer Community as a place for you to collaborate with FireEye and other like-minded builders. We are a team of developers, and we understand the frustration of trying to work with code and having nowhere to turn for help. The community was built so that you not only have direct communication with our product and engineering teams but so you can have a place to find each other online and get answers to questions. How great is it when you ask a question and a kind stranger says "Hey, I've had that problem! Here was my solution..."?

Not only that, but we encourage you to come and share the things you've built before ever being asked. Come and show what you've built, how and why you built it, and get feedback from FireEye and others in the community.

You can also use the community to suggest new features. Have you ever used an API and thought, "I really wish this could do X."? This is your place to say that. You can even vote on the ideas you like the most, so we know what the community as a whole is most interested in.

In short, if you have something to say, then the FireEye Developer Community is the place to come share it. If you don't feel comfortable posting or sharing, then you are more than welcome to reach out to us.

SDKs, Tools, and Docs

We understand that, when it comes to code, getting started with us has been difficult. That is why we are now dedicating resources to help decrease your time-to-value as a developer. There are several things we are going to start building to address this:

First, we are creating better, interactive documentation around our product APIs. We have a lot of great API capabilities across our various products and services, and we want you to have one place, the Developer Hub, to learn about and interact with those APIs. We'll be using these API docs to better articulate what our APIs can do and how best to work with them in your solutions. Use the FireEye Developer Community as a sounding board to share where we need to make improvements to support your API use cases.

Second, we are building a suite of client SDKs across the most popular computer languages to make it easier than ever for you to interface with the FireEye products of your choice. It will take time to roll out support for all languages and all products, but our client libraries will be MIT licensed and stored in GitHub. You will be able to contribute to those projects as you see fit and help to improve the workflow not only for yourself, but for others as well. We ♥ Open Source!

Finally, we'll provide a public place for FireEye teams (including our Developer Relations team) to build tools that will help make integrating with FireEye even faster. Some examples of tools we may introduce are things such as:

  • FireEye Security Orchestration Plug-in Generator – A tool to design your own FSO plug-ins on Windows, Mac, or Linux. Use it to generate the plugin and unit test boilerplate, then fire up your preferred editor or IDE to build and test the integration logic. Now available in the FireEye Market!
  • Helix Parser Tool - A tool to upload the log that you would like Helix to recognize, write a parser that understands your log, and then push that parser to Helix. We want to put the power of Helix log parsing in your hands. Stay tuned for further updates.
  • Have a tool in mind that you'd like to request? We're here to make your lives better, so reach out to us and let us know what we can build for you!

Content

People tend to support that which they help build. When you get to watch something being built and can contribute to the conversation, you ultimately feel more connected to it. This isn't a tool to trick you into wanting to be here—we want to build something for you and by you! To us, this means two things:

First, as we build the FireEye Developer Hub, we want your feedback. We will document what we are building as we are building it, and we openly welcome you to give feedback when you see fit. We will share the build progress of our hub on our FireEye Developer Blog, our @FireEyeDev Twitter, the FireEye Developer Community, and other possible locations yet to be determined. You can reach out to us on any of those platforms and let us know your thoughts, or you can email us at developers@fireeye.com. We will do alpha and beta testing of our SDKs, tools, and even the FireEye Developer Hub itself. If you are interested in taking part in those things, let us know!

Second, but certainly not the least, we will be generating content that covers all code-related aspects of our products. This content will come in the form of docs, blog posts, videos, and anything else that you might request. Ultimately, we are here to serve you, and we are happy to provide content in a way that suits you best. Let us know if you have a preferred way of consuming content by reaching out to us on any of the platforms listed above. Now, let's get to building—together!