This repository has been archived by the owner on Jun 26, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 33
/
future-features.txt
51 lines (42 loc) · 2.1 KB
/
future-features.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
* Basic Policy language implementation
** Multi-threaded Datalog implementation
** Bottom-up datalog evaluation
** Query optimization
** Materialized implementation: automated view selection/inlining
* Enhanced Policy language
** ActiveDirectory facade
** Syntax improvements (modals like insert/delete)
** Support for compound objects (safe, stratified recursion)
** Richer support for describing actions in Enforcement policy
** Modules
* Policy structure
** Multi-tenant
** Multi-stakeholder (tenants, finance, operations, etc.)
* Enforcement
** Execution of (rich) actions
** Carve out subpolicies and push to other components, e.g. Neutron
** Add consultation with Congress to other OS components, e.g. Nova/Neutron
** Proper remediation enumeration with Classification+Action policies
** Find ways of automatically choosing the proper remediation strategy (e.g. priorities/monotonicity)
** Give cloud owner way of configuring how proactive/reactive/etc. based on information from separate policies.
* Libraries
** Data source drivers for common OS and non-OS components
** HIPAA, etc. encoding
** Ontologies for different sectors, e.g. finance
* Policy Analysis
** Look for infinite loops through Enforcement policy (using Action policy)
** Compare Access control policy and Classification policy for redundancy
** Change impact analysis
* Dashboard
** IDE for policy (different levels: raw-Datalog, AD, checkbox-based)
** List violations
** Explain violations (step-by-step tracing through policy)
** Simulate state change and action execution
** Enumerate remediations for a given violation
* Architecture and API
** Formalize and implement full introspection and query APIs
** Distribute across multiple nodes
** Ensure Congress can use another Congress instance as data
* Authentication and Access Control
** Add authentication and access controls on API/dashboard
** When remediating, which user(s) are executing actions? Does Congress need admin credentials for all its cloud services or are user credentials part of actions? Need proper storage for those credentials. Etc.