Article Summary: I would like to introduce complyctl, a new command-line utility available since Fedora 42, designed to streamline security compliance for Fedora users. It highlights how complyctl leverages the “ComplianceAsCode” approach with a flexible plugin system (including OpenSCAP) to automate and standardize compliance checks, making them faster, more accurate, and easily integrated into workflows.
Article Description: The plan is to provide a comprehensive overview of complyctl’s features, emphasizing its role in automating compliance checks, ensuring accuracy with OSCAL, and its extensibility through plugins like the OpenSCAP plugin. After the context, I would also like to share a practical, step-by-step tutorial to guide users through installation and the compliance workflow (list, plan, generate, scan), demonstrating how to efficiently maintain a robust security posture on Fedora systems.
https://discussion.fedoraproject.org/t/article-proposal-introducing-complyctl-for-effortless-compliance-in-fedora/164125
Hi, it is saved as Draft. Should I "Submit for Review" or is it done by a reviewer?
Link: https://fedoramagazine.org/?p=42553&preview=true&preview_id=42553
@marcusburghardt The link is all you need to trigger the next steps. The editors will review and let you know the status as things progress.
By the way, if you have suggestions for a feature image to attend this article let us know. Otherwise we will develop something for it.
Thank you.
Metadata Update from @rlengland: - Custom field preview-link adjusted to https://fedoramagazine.org/?p=42553&preview=true&preview_id=42553
@marcusburghardt I've done a first pass on the article (visual/formatting no verbiage yet) and I think the table in section "3. Step-by-Step Tutorial" is not very pleasing. Is it possible that it could be replaced by a "screen capture" of a similar table? If you need assistance with that and can provide the image as an attachment in this ticket we can help make the replacement.
Metadata Update from @rlengland: - Custom field editor adjusted to rlengland
@marcusburghardt I've reviewed and edited your article. I modified some text to remove passive voice and broke up some long sentences to improve readability. It would be good if you can give it a review to make certain I haven't modified your intent by accident.
If you can address that table issue I mentioned earlier, and make any further edits you wish to make, I think we are close to publication.
@rlengland , thanks for prompt review. I just checked your suggestions and the text is still accurate. I also replaced the table with a "screen capture" from a testing VM. Just attached the image here as well just in case.
@marcusburghardt The image looks great. Thank you for that. I will be adding a featured image and scheduling this for 17 September.
Thank you for your contribution to the Fedora Magazine.
Metadata Update from @rlengland: - Custom field image-editor adjusted to rlengland - Custom field publish adjusted to 2025-09-17
Metadata Update from @rlengland: - Issue untagged with: needs-image
@marcusburghardt The image looks great. Thank you for that. I will be adding a featured image and scheduling this for 17 September. Thank you for your contribution to the Fedora Magazine.
Great news @rlengland. I appreciate your support and all the work this team is doing here. My experience proposing this article was very positive and I am looking forward to the next contribution. : ) Cheers
Hi @rlengland , I received a feedback about some typos missed along the process but I can't fix them directly.
Could you help with this, please? 1 - In "Optionally, you can also include the –plain option for simplified output." it should include two dashes in "--plain". I believe they were unified when rendering.
2 - In "2. Accuracy and Consistency:" is missing a "d" in "standarization" "standarization" -> "standardization"
3 - In the Step 2: Create an Assessment Plan "cusp-fedora" -> "cusp_fedora", with the underline character instead of dash "complyctl plan cusp_fedora"
Thanks
@marcusburghardt Yes, once published the editors must make changes. I've corrected the issues. In addition found another -- (two en dashes) which were collapsed into an em dash (one long dash).
Issue status updated to: Closed (was: Open) Issue close_status updated to: published