Import / export enchantement about pwndoc-ng HOT 3 OPEN

Update

I've implemented Import/Export of Companies, Clients and Collaborators.

There is a lot of foreign keys for each categories, ie: a backup of clients won't save their companies. Therefore imported clients will not have any companies associated.

Open questions

1. What do you expect from Templates import/export since you already can save them from the frontend ? A massive dump (lets say a zip ?) of docx + configuration ?

2. According to the number of foreign keys (creator, reviewers, company, findings, ...) How do you see Audits import/export ? For now, Audit and Findings are 2 separated objects, but we might bee able to create a custom import/export parser.

3. What about a "Full copy" which will copy the full MongoDB that you could import/export ?

4. What do you think about a python script to facilitate migration between old pwndoc/pwndoc-ng and latest pwndoc-ng (API based) ?

cc @RobertDoc @Serizao @Syzik @TheZ3ro

from pwndoc-ng.

1. What do you expect from Templates import/export since you already can save them from the frontend ? A massive dump (lets say a zip ?) of docx + configuration ?

I don't expect much for that, as you would probably save them outside of Pwndoc-ng anyway (eg. on a file share).

2. According to the number of foreign keys (creator, reviewers, company, findings, ...) How do you see Audits import/export ? For now, Audit and Findings are 2 separated objects, but we might bee able to create a custom import/export parser.

Looks important for companies.

3. What about a "Full copy" which will copy the full MongoDB that you could import/export ?

Could be the easiest for failure or new instance restoration. But it's nice to still have vulnerabilities or Custom data independently.

4. What do you think about a python script to facilitate migration between old pwndoc/pwndoc-ng and latest pwndoc-ng (API based) ?

If you mean from pwndoc to pwndoc-ng, if you write such a script, you could share it on https://github.com/noraj/Pentest-collab-convert.

Collection of scripts used to convert stuff from one penetration testing collaborative platform to another and facilitate the migration of solution

from pwndoc-ng.

1. What do you expect from Templates import/export since you already can save them from the frontend ? A massive dump (lets say a zip ?) of docx + configuration ?

I don't know how often one export a single template. IMHO a zip with docx files and the template configurations would be awesome. Or even a way to export the template configurations themselves (custom sections, custom fields, etc) that are missing from the frontend export IIRC.

2. According to the number of foreign keys (creator, reviewers, company, findings, ...) How do you see Audits import/export ? For now, Audit and Findings are 2 separated objects, but we might bee able to create a custom import/export parser.

To be honest I think an audit export will need to resolve the foreign keys links and export a single "json" (we can think about the proper format) with all the meaningful data about the audit

3. What about a "Full copy" which will copy the full MongoDB that you could import/export ?

I would like this feature. Also for "external backup" purposes in case the MongoDB gets corrupted during updates or such

4. What do you think about a python script to facilitate migration between old pwndoc/pwndoc-ng and latest pwndoc-ng (API based) ?

I vouch for this as well. Ideally it could parse the MongoDB directly and implement the "Full copy" feature discussed above.

from pwndoc-ng.