netanelcyber / netanelcyber/AdPentestAI-Python

Mock AD environment for CI/CD testing

Open
#14 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

ci-cd docker help-wanted testing v1.1.0
Dominant language
Python
Stars
5
Forks
2
Avg merge
22h 25m
Merged PRs (30d)
7

Description

Description

Build containerized mock Active Directory environment for automated CI/CD pipeline testing without requiring real AD infrastructure.

Components

  1. Windows Server 2022 Container

    • Active Directory Domain Services
    • DNS server (configured for domain)
    • LDAP listening on 389/636
    • Kerberos on 88
  2. Exchange Server Mock

    • SMTP server (port 25, 587, 465)
    • POP3 server (port 110, 995)
    • IMAP server (port 143, 993)
    • EWS endpoints (HTTPS)
  3. Test Data

    • Sample AD users and groups
    • Service Principal Names (SPNs)
    • ADCS certificate templates
    • Exchange mailboxes

Implementation

  • Docker Compose orchestration
  • Minimal resource footprint (~4GB)
  • Startup time < 60 seconds
  • Pre-populated with test data
  • Health check endpoints

Files to Create

  • docker-compose.test.yml
  • docker/ad-mock/Dockerfile
  • docker/exchange-mock/Dockerfile
  • scripts/setup-test-data.ps1
  • .github/workflows/integration-tests.yml

Success Criteria

  • Full AD environment spins up in < 60s
  • All framework tools can target it successfully
  • Used in automated CI/CD pipeline
  • Supports parallel test execution

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the requested files: docker-compose.test.yml, both Dockerfiles, scripts/setup-test-data.ps1, and .github/workflows/integration-tests.yml. Define how the mock AD and Exchange components, test data, health checks, and orchestration fit together before implementation. Done means the environment starts within 60 seconds, supports the listed services and test data, and runs in CI with parallel tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, docker-compose, github-actions, powershell
Domain
ci-cd, devops, infrastructure, security, testing
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.