Merge pull request #221 from KennaSecurity/add_meta_directory

Creation of a Directory for Meta files

Sample KDI meta files/Panoptica meta file.csv

@@ -0,0 +1,43 @@
+Kenna Item,Associated Source File Column,Required,Description,Object Type
+date_format,%Y-%m-%d %H:%M:%S.%6N%:z,,,
+locator,hostname,,field used to compare for dupes for this file load only,Asset
+file,,One locator required per asset,(string) path to affected file,Asset
+ip_address,,One locator required per asset,(string) IP of internal facing asset,Asset
+mac_address,,one value per Asset is required,(mac format-regex) MAC address asset,Asset
+hostname,asset__name,one value per Asset is required,(string) host name/domain name of affected asset,Asset
+container_id,,one value per Asset is required,(string) container identifier of affected asset,Asset
+image_id,,one value per Asset is required,(string) image identifier of affected asset,Asset
+ec2,,one value per Asset is required,(string) Amazon EC2 instance id or name,Asset
+netbios,,one value per Asset is required,(string) netbios name,Asset
+external_ip_address,,no,(string) IP of external facing asset,Asset
+url,,one value per Asset is required,(string) URL pointing to asset,Asset
+fqdn,,one value per Asset is required,(string) fqdn of asset,Asset
+external_id,asset__uid,one value per Asset is required,(string) ExtID of asset-Often used as an int org name for asset,Asset
+database,,one value per Asset is required,(string) Name of db,Asset
+application,,no,(string) ID/app Name,Asset
+tags,"asset__env_type,asset__resource_type__name,",no,(string) list of strings that correspond to tags on an asset,Asset Meta
+tag_prefix,"AssetEnvType: ,AssetResourceType: ,",,,
+owner,,no,(string) Some string that identifies an owner of an asset,Asset Meta
+os,,no,(string) Operating system of asset,Asset Meta
+os_version,,no,(string) OS version,Asset Meta
+priority,,no,(Integer) Def:10 - Priority of asset (int 1 to 10).Adjusts asset score. nil for default to 10,Asset Meta
+scanner_source,static,yes,declares scanner type data locatin as static (listed in this file) or column (pulled from the source file),
+scanner_type,Panoptica,yes,(string) - official name of scan type - should be the same across files where appropriate can be static or pulled from column,Vulnerability
+scanner_id,cveID,yes,(string) - Vuln ID defined by the scanner,Vulnerability
+details,exploits,no,(string) - Details about vuln,Vulnerability
+created,,no,(string) - Date vuln created,Vulnerability
+score_map,,no,hash of translation scanner score values to kenna range of 1-10 if needed,
+scanner_score,cvssSeverity,no,(Integer) - scanner score,Vulnerability
+last_fixed,,no,(string) - Last fixed date,Vulnerability
+last_seen,,yes,,Vulnerability
+status_map,,no,hash of translation scanner status to Kenna status mappings if needed,
+status,,yes,"(string) default to ""open"" if inbound reports will only include open vulns",Vulnerability
+closed,,required if status is closed,(string) Date it was closed,Vulnerability
+additional_fields,,no,(array) Comma delimited findings (new appsec only),Findings
+port,,no,(Integer) Port if associated with vuln,Vulnerability
+cve_id,cveID,no,(string) Any CVE(s)?,Vuln Def
+wasc_id,,no,(string) Any WASC?,Vuln Def
+cwe_id,,no,(string) Any CWE?,Vuln Def
+name,,no,(string) Name/title of Vuln,Vuln Def
+description,summary,no,(string) Description,Vuln Def
+solution,mitigation,no,(string) Solution,Vuln Def

Sample KDI meta files/README.md

@@ -0,0 +1,5 @@
+# Meta Files Repository
+The Cisco Vulnerability Management platform is capable of ingesting data from any structured dataset in CSV format. It utilizes a converter utility to transform this data into a JSON file, formatted specifically to enable customers to import asset and vulnerability data into the platform. A meta file is needed for this conversion and needs to be done once for each data set being ingested. 
+
+The purpose of this directory is to act as a repository, providing customers with access to conversion files that have been developed for various scanning platforms. Although these files are designed to be used directly where possible, some customers may find that adjustments are necessary to align with the particulars of their environment or their unique use case.
+