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.

Sign up for GitHub

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

Jump to bottom

Cloud Node APIs for V2 #838

Closed
jatin-baweja opened this issue Jan 23, 2023 · 0 comments
Closed

Cloud Node APIs for V2 #838

jatin-baweja opened this issue Jan 23, 2023 · 0 comments
Assignees
@jatin-baweja
Labels
enhancement New feature or request needs-triage Indicates that issue is not yet triaged and assigned v2 ThreatMapper revamp based on neo4j integration

Comments

@jatin-baweja
Copy link
Contributor

Adding Cloud Node Register and List APIs:

Flow:

  1. User deploys Deepfence cloud-scanner on the cloud provider of their choice(AWS, GCP, Azure).
  2. Cloud Scanner registers itself on the console(using the cloud nodes register API).
  3. While registering, cloud scanner also checks for pending scans from the console.
  4. Once registered, the cloud node appears on the console under Posture(using the cloud nodes list API)
@jatin-baweja jatin-baweja added enhancement New feature or request needs-triage Indicates that issue is not yet triaged and assigned v2 ThreatMapper revamp based on neo4j integration labels Jan 23, 2023
@jatin-baweja jatin-baweja self-assigned this Jan 23, 2023
@jatin-baweja jatin-baweja mentioned this issue Jan 23, 2023
Merged
gnmahanth pushed a commit that referenced this issue Jan 23, 2023
@jatin-baweja
Add Cloud Nodes Register and List API #838 (#839)
40ca5c3 
* Add APIs to register and list cloud nodes

* Add debug logs and total count to cloud node account list

* Remove commented code, cleanup unused code, move cloud provider constant
jatin-baweja added a commit that referenced this issue Feb 6, 2023
@jatin-baweja
Add Start Cloud Compliance Scan API to v2 #838
9e87981
jatin-baweja added a commit that referenced this issue Feb 6, 2023
@jatin-baweja
Add Start Cloud Compliance Scan API to v2 #838 (#866)
9d0f493
jatin-baweja added a commit that referenced this issue Feb 8, 2023
@jatin-baweja
Add Bulk Cloud Compliance Status API #838 (#873)
25efe1e 
* Add ingest scan status and scan status API for cloud compliance scans

* Merge cloud compliance and compliance start scan APIs and make status response for cloud compliance and compliance consistent

* Fix Malware scan request and add linux to node_types for compliance start scan API

* Replace hard coded strings and removing start cloud compliance API from docs
jatin-baweja added a commit that referenced this issue Feb 8, 2023
@jatin-baweja
Move cloud compliance scan start to compliance scan start function #838
302b899
jatin-baweja added a commit that referenced this issue Feb 9, 2023
@jatin-baweja
Add cloud compliance scan results API #838
af3dffd
jatin-baweja added a commit that referenced this issue Feb 9, 2023
@jatin-baweja
[v2] Update compliance scan start request to include filters #838 (#881)
0b24284 
* Update compliance start request to include filters

* Update golang deepfence sdk to include cloud_account and kubernetes_cluster node types

* Add edge cases for start scan filter conditions

* Add filtered nodes as per updated criteria

* Update get_node_ids response on empty where condition
jatin-baweja added a commit that referenced this issue Feb 9, 2023
@jatin-baweja
Add cloud compliance scan results API #838 (#884)
70b31a3
jatin-baweja added a commit that referenced this issue Feb 9, 2023
@jatin-baweja
Add stats to cloud compliance results API and add node information to…
ea314a8 
… cloud compliance status API #838
jatin-baweja added a commit that referenced this issue Feb 9, 2023
@jatin-baweja
Update ComplianceScanStatus to ComplianceScanInfo #838
4d6260b
jatin-baweja added a commit that referenced this issue Feb 10, 2023
@jatin-baweja
Update benchmark type and compliance percentage for cloud compliance …
915cbbd 
…scan results API #838
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jatin-baweja jatin-baweja

Labels
enhancement New feature or request needs-triage Indicates that issue is not yet triaged and assigned v2 ThreatMapper revamp based on neo4j integration
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jatin-baweja @ramanan-ravi