Monitoring Open Ports per WSO2 Security Guidelines
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 99
- Forks
- 708
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 22
Description
Description
Hi Team,
The current “Check open ports and services” guideline under Network-level Security in the Security Guidelines for Production Deployment documentation [1] needs to be updated to reflect the correct approach, including considerations for dynamic ports. Additionally, all required ports should be accurately documented in [2], as the current list does not include ports such as 10711, 8099, 9021, 8021, and 8672.
[1] https://apim.docs.wso2.com/en/4.3.0/install-and-setup/setup/deployment-best-practices/security-guidelines-for-production-deployment/#network-level-security
[2] https://apim.docs.wso2.com/en/4.3.0/install-and-setup/setup/reference/default-product-ports/#api-m-ports
Thanks,
Sameera
Version(s)
4.6.0, 4.5.0, 4.4.0, 4.3.0, 4.2.0, 4.1.0, 4.0.0
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Network-level Security section and the API-M ports reference page, then compare the documented guidance and port list with the requirements described in the issue, including dynamic ports. Done means both linked documentation areas accurately describe the approach and required ports, including 10711, 8099, 9021, 8021, and 8672.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, networking, security
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100