Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Import feature - api endpoint #1356

Open
KlavsKlavsen opened this issue Jan 13, 2025 · 1 comment
Open

Import feature - api endpoint #1356

KlavsKlavsen opened this issue Jan 13, 2025 · 1 comment
Labels
integration question Further information is requested

Comments

@KlavsKlavsen
Copy link

KlavsKlavsen commented Jan 13, 2025

Problem statement
I would love to be able to point to an API to get list of assets, applied controls, risk scenarios etc.

Expected behavior
This way I could automate the lists I work with - f.ex. by pointing that to my CMDB.. (and writing a function to respond in CISO compatible way) - and you could add specific CMDBs support in pro edition if you wanted.

Same way, I could point to openvas, openscab or other open source tools - that provide a list of "risks".. kube-bench f.ex. for k8s security benchmark finds.

Also point it to something getting all public certs issued for my domains (as those are a clear risk too).

its merely an idea at this point.. but the data (such as servers and services on them - often identified by certs) shouldn't have to be manually entered as that will easily become stagnant and wrong.

Such api and data standard would allow other open source tools to provide data, always updated - to CISO - helping to keep the security "in check" - and ciso could alert on new un-mitigated risks f.ex. (from a security scanner) etc.

@KlavsKlavsen KlavsKlavsen added the question Further information is requested label Jan 13, 2025
@ab-smith
Copy link
Contributor

Hello @KlavsKlavsen and thank you for the inputs,
This is indeed part of our next phase for the product around integration. We've finalised a first drafit for the design that we'll be presenting during the office hours live sessions.
Essentially, the automation will be handled externally on an orchestrator of your choice (we'll suggest one based on the community votes with samples and let people contribute to that) and the orchestrator will just have to send a message to a broker on which CA will be listening to process events asynchronously, which will scale way better on the long run. We'll just impose the message schemas.
Let me know if this is is what what you had in mind.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
integration question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants