gfwleak/tango-maat
Archived
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

rename o2o and object2object to object_group

Browse Source
This commit is contained in:
root
2024-10-24 07:56:49 +00:00
parent 1cd21a43c9
commit da715f21ef
22 changed files with 311 additions and 311 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/getting_started.md
View File

@@ -31,7 +31,7 @@ A complete use case consists of three parts:
### Case1
In the scanning scenario, it is necessary to configure the schema of multiple tables, including the item table, object2rule table, and rule table. If there is also object nesting involved, the schema of the object2object table needs to be configured.
In the scanning scenario, it is necessary to configure the schema of multiple tables, including the item table, object2rule table, and rule table. If there is also object nesting involved, the schema of the object_group table needs to be configured.
**(1) table schema**
@@ -67,8 +67,8 @@ Table schema is stored in a json file(such as table_info.json), which is loaded
},
{
"table_id":2,
"table_name":"OBJECT2OBJECT",
"table_type":"object2object",
"table_name":"OBJECT_GROUP",
"table_type":"object_group",
"valid_column":4,
"custom": {
"object_id":1,
@@ -100,7 +100,7 @@ Configurations are stored in a json file(such as maat_json.json), which is loade
{
"rule_table": "RULE",
"object2rule_table": "OBJECT2RULE",
"object2object_table": "OBJECT2OBJECT",
"object_group_table": "OBJECT_GROUP",
"rules": [
{
"rule_id": 123,
@@ -217,7 +217,7 @@ In the callback scenario, only the schema of the corresponding table needs to be
{
"rule_table": "RULE",
"object2rule_table": "OBJECT2RULE",
"object2object_table": "OBJECT2OBJECT",
"object_group_table": "OBJECT_GROUP",
"plugin_table": {
"table_name": "TEST_IP_PLUGIN_WITH_EXDATA",
"table_content": [