| Event Id | 9186 |
| Source | MSExchangeSA |
| Description | Microsoft Exchange System Attendant has detected that the local computer is not a member of group cn=Exchange Domain Servers,cn=Users,dc=microsoft,dc=com. System Attendant is going to add the local computer into the group. The current members of the group are CN=SERVERNAME,OU=NEWOU,DC=microsoft,DC=com; . |
| Event Information | After you move a Microsoft Exchange 2000 Server computer from one organizational unit to another within the domain, or after you rename the organizational unit, the above event with 9187 event id, are logged in the application event log. |
| Reference Links | System Attendant Generates 9186 and 9187 Event ID Messages |
| Event Id | 9187 |
| Source | MSExchangeSA |
| Description | Microsoft Exchange System Attendant failed to add the local computer as a member of the DS group object name. Please stop all the Microsoft Exchange services, add the local computer into the group manually and restart all the services. |
| Event Information | Explanation : This event indicates that the System Attendant has detected that the local computer is not a member of the Exchange Domain Servers Security Group and failed to add it to that group. While there may be other causes of this error, it can happen because the Distinguished Name (DN) of the Server has changed. This change in the DN can happen because the computer may have been moved to another organizational unit (OU) in Active Directory. This error may show up if even if the server is in the Exchange Domain Servers Security Group. User Action : Stop all Exchange services. If necessary, add the local computer to the Exchange Domain Servers Security Group and restart the System Attendant Service manually. Note that this will cause the Information Store service to restart. </p> |
| Reference Links | System Attendant Generates 9186 and 9187 Event ID Messages |
MODULE 1
Topic: Secure Development LifeCycle And Chain of Security Tools.
Description: This module mainly focuses on the introduction of security terminology and attacking vectors involved in an application. It also provides an overview of application architecture and the role of different tools involved during the entire course. Its content provides an offensive security methodology from a secure development perspective.
Topics Covered:
Module 1 Exercises:
MODULE 2
Topic: Deserialization Issues in JAVA, Testing, and Mitigating
Description: This module focuses on the different annotation features provided by Spring Boot and develop serialization-deserialization functionality in your API. It provides an overview of the issues related to deserialization in JAVA and how to mitigate these flaws in your API development, as well as different techniques to mitigate input validation bypass issue. It also covers creating custom extensions on ZAP.
Topics Covered:
Module 2 Exercises:
MODULE 3
Topic: Security Configuration in Spring Boot and Active Scanning using ZAP
Description: This module focuses on implementing the scope-based authorization features of Spring Boot, secure configuration of an API, along with restricting end-points and internal methods. Moreover, it presents blacklisting of potential dangerous commands in your API Introduction to active scanning feature of ZAP tool.
Topics Covered:
Module 3 Exercises:
FINAL EXAM
In this final exercise, you would work on the offensive and defensive side of security, attacking your own developed APIs and mitigating the issues found during your attack.
If any security issues are found during the test, mitigate/fix them and provide a PoC on the fix.
Evaluation would be based on the number of implemented features from the above-mentioned exercise and on the number of vulnerabilities found and mitigated in the report.
Source : https://pentestmag.com/product/purple-teaming-in-java-api-development/
