diff --git a/Jieyab-Report-Template/OSINT Report.md b/Jieyab-Report-Template/OSINT Report.md new file mode 100644 index 0000000..a40774c --- /dev/null +++ b/Jieyab-Report-Template/OSINT Report.md @@ -0,0 +1,5 @@ +SOON + +# Read full here for detail also template docx + +https://jieyab89-osint.gitbook.io/ \ No newline at end of file diff --git a/Jieyab-Report-Template/OSINT-Report.md b/Jieyab-Report-Template/OSINT-Report.md deleted file mode 100644 index a6e0cc1..0000000 --- a/Jieyab-Report-Template/OSINT-Report.md +++ /dev/null @@ -1 +0,0 @@ -SOON \ No newline at end of file diff --git a/Jieyab-Report-Template/Penetration Testing Report.md b/Jieyab-Report-Template/Penetration Testing Report.md index ebe1edd..3a74698 100644 --- a/Jieyab-Report-Template/Penetration Testing Report.md +++ b/Jieyab-Report-Template/Penetration Testing Report.md @@ -3,6 +3,7 @@ A penetration testing report is the primary deliverable of a security assessment and serves as a formal record of the testing activities, findings, and recommendations. Beyond documenting technical vulnerabilities, the report should provide clear, structured, and actionable information that can be understood by both technical teams and management. A well-prepared report not only demonstrates the results of the assessment but also helps organizations prioritize remediation efforts, improve their security posture, and support compliance or audit requirements. The following sections describe the key elements that should be included in a professional penetration testing report, along with their purpose and importance throughout the reporting process. + # Title The report title is the first element readers will see and should clearly describe the purpose and scope of the document. A well-defined title helps distinguish the report from other technical documents while immediately communicating the type of security assessment that was performed. The title should be concise, professional, and consistent with the organization's reporting standards. @@ -314,6 +315,6 @@ The issuance of this report confirms that the authorized parties listed below ha - Electronic or digital signatures may be accepted where permitted by the organization's policies and applicable regulations. - Any modification to this report after approval must be documented and re-approved by the relevant authorized parties. -# Read full here +# Read full here for detail also template docx https://jieyab89-osint.gitbook.io/jieyab89-osint-cheat-sheet-wiki-tips/osint-tool-resouces-usage/all-about-reporting \ No newline at end of file diff --git a/Jieyab-Report-Template/Readme.md b/Jieyab-Report-Template/Readme.md index 5f02c44..4a4b82d 100644 --- a/Jieyab-Report-Template/Readme.md +++ b/Jieyab-Report-Template/Readme.md @@ -1,3 +1,3 @@ -# Welcome to Jieyaab Template Reprot +# Welcome to Jieyab Template Report Containing information and important, required elements for the report, here is a sample report from Jieyab. You can customize the attached template. I will keep updating it whenever there are updates or audits to the report template \ No newline at end of file diff --git a/README.md b/README.md index 13e5642..9f460ca 100644 --- a/README.md +++ b/README.md @@ -1904,6 +1904,9 @@ For this case u must know the context also dorking for better results - [fansearch](https://www.fansearch.com/) - [xmodelfinder](https://www.xmodelfinder.com/) - [sotugas onlyfans search username](https://sotugas.com/onlyfans/) +- [trakteer](https://new.trakteer.id/) You must to dork +- [patreon](https://www.patreon.com/) You must to dork +- [weibo](https://weibo.com/) You must to dork Pro Tips