One of the most powerful features inside of PassiveTotal is the ability to monitor infrastructure and receive alerts when something changes. We’ve covered how to deploy monitors in previous postings and videos, but never showed how they could be used for follow-up actions. By combining the notifications and monitors API from the account endpoints, it’s easy to create an automated system to block or publish threat data.
For the past several years, IBM’s QRadar has been recognized as a leader in Gartner’s Magic Quadrant for SIEM and Log Management. RiskIQ is the cornerstone of External Threat Management programs for many of the largest enterprises in the world. In December of 2015, IBM launched the Security App Exchange that allowed companies to begin creating applications that could enhance the QRadar experience. Today, RiskIQ’s PassiveTotal is excited to announce the release
For the past several years, CRITs has provided analysts with a free, open source alternative to a hosted threat intelligence platform. When support for external services went public, PassiveTotal was quick to draft up a service and release it to the community. A lot has changed since then, both in CRITs and most notably, the data that PassiveTotal provides. With our new API released, we felt it was time to update our existing service which
A decent portion of PassiveTotal usage comes from the API and other 3rd-party integrations we have, so in building our new API, we wanted to make it easy for developers to get access to our data in as many forms as possible. Packed into our Python client are several libraries representing each major data type we have. The thought behind this was that users could selectively implement only the sources of data they found most
Building a scalable API means having a deep understanding of your users' usage patterns. Over the past few months, we have made significant changes to our application architecture to meet our communities needs and as a final piece to the puzzle, we are releasing a new foundation for all our future APIs. We recognize updating code to use a new API is never fun, so we tried to make it easier by building an extensive