Automate CyCAT.org
HumDay reads CyCAT.org’s own published API description and derives 14 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What CyCAT.org is
CyCAT - The Cybersecurity Resource Catalogue public API services.
What HumDay can do in CyCAT.org
1 documented operations change something in CyCAT.org.
- POSTPropose new resource to CyCAT.
/propose
What HumDay can read from CyCAT.org
These are the operations a schedule or a trigger can watch.
- GETList all known namespaces.
/namespace/getall - GETGet parent UUID(s) from a specified project or item UUID.
/parent/{uuid} - GETFull-text search in CyCAT and return matching UUID.
/search/{searchquery} - GETGet information about the CyCAT backend services including status, overall statistics and version.
/info - GETGenerate an UUID version 4 RFC4122-compliant.
/generate/uuid - GETGet child UUID(s) from a specified project or publisher UUID.
/child/{uuid} - GETLookup UUID registered in CyCAT.
/lookup/{uuid} - GETGet relationship(s) UUID from a specified UUID.
/relationships/{uuid} - GETList projects registered in CyCAT by pagination (start,end).
/list/project/{start}/{end} - GETList publishers registered in CyCAT by pagination (start,end).
/list/publisher/{start}/{end} - GETGet all ID from a given namespace.
/namespace/getid/{namespace} - GETGet relationship(s) UUID from a specified UUID including the relationships meta information.
/relationships/expanded/{uuid} - GETGet all known UUID for a given namespace id.
/namespace/finduuid/{namespace}/{namespaceid}
How automating CyCAT.org works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
- See it proven. The program runs and shows you the result before it is allowed near your live CyCAT.org account.
- Grant access, then go live. You approve the specific CyCAT.org operations it may use — and only those.
Automate CyCAT.org with these
- Cloudflare3122 operations
- IX API IX78 operations
- N Auth nextAuth55 operations
- Conjur41 operations
- Credas37 operations
- Cisco PSIRT openVuln19 operations
- Users (Okta )19 operations
- 1Password Connect15 operations
- Swagger for Patrowl Engines14 operations
- Appspot Authentiq12 operations
- Testfire AltoroJ12 operations
- hashlookup CIRCL11 operations
Categories
Questions about CyCAT.org automation
- Can HumDay connect to CyCAT.org?
- Yes. HumDay reads CyCAT.org's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 14 operations are documented.
- Do I need to write code to automate CyCAT.org?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your CyCAT.org account.
- What can HumDay do in CyCAT.org?
- 1 of the 14 documented operations change something in CyCAT.org, and 13 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my CyCAT.org account safe?
- Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to CyCAT.org is held behind that approval.
Where this came from
The operations above are read from a published API description for CyCAT.org at api.cycat.org/swagger.json. Descriptions are the provider’s own words, not ours. Last published 2021-06-21.