Skip to content

Actions: VeriDevOps/ARQAN.action

Actions

ARQAN map issue

Actions

Loading...
Loading

Show workflow options

Create status badge

Loading
arqan.yaml
9 workflow runs
9 workflow runs

Filter by Event

Filter by Status

Filter by Branch

Filter by Actor

secure password wifi ARQAN map issue #9: Issue #10 labeled by agilebotanist
October 25, 2024 15:26 17s
October 25, 2024 15:26 17s
Identify and authenticate all users (humans, software processes and devices), prior to allowing them access to the system or assets. ARQAN map issue #8: Issue #9 labeled by agilebotanist
February 26, 2024 13:03 15s
February 26, 2024 13:03 15s
Enforce the assigned privileges of an authenticated user (human, software process or device) to perform the requested action on the system and monitor the use of these privileges. ARQAN map issue #7: Issue #8 labeled by agilebotanist
February 26, 2024 13:01 17s
February 26, 2024 13:01 17s
The access via untrusted networks requirements are component-specific and can be located as requirements for each specific component type. ARQAN map issue #6: Issue #7 labeled by agilebotanist
February 23, 2024 22:19 19s
February 23, 2024 22:19 19s
The access via untrusted networks requirements are component-specific and can be located as requirements for each specific component type. ARQAN map issue #5: Issue #6 labeled by agilebotanist
February 23, 2024 22:14 11s
February 23, 2024 22:14 11s
The access via untrusted networks requirements are component-specific and can be located as requirements for each specific component type. ARQAN map issue #4: Issue #5 labeled by agilebotanist
February 23, 2024 22:11 11s
February 23, 2024 22:11 11s
The access via untrusted networks requirements are component-specific and can be located as requirements for each specific component type. ARQAN map issue #3: Issue #4 labeled by agilebotanist
February 23, 2024 22:08 12s
February 23, 2024 22:08 12s
The access via untrusted networks requirements are component-specific and can be located as requirements for each specific component type. ARQAN map issue #2: Issue #3 labeled by agilebotanist
February 23, 2024 22:04 13s
February 23, 2024 22:04 13s
The access via untrusted networks requirements are component-specific and can be located as requirements for each specific component type. ARQAN map issue #1: Issue #2 labeled by agilebotanist
February 23, 2024 21:57 12s
February 23, 2024 21:57 12s