Skip to content

Actions: VeriDevOps/ARQAN.action

Actions

All workflows

Actions

Loading...
Loading

Showing runs from all workflows
18 workflow runs
18 workflow runs

Filter by Event

Loading

Filter by Status

Loading

Filter by Branch

Loading

Filter by Actor

Loading
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
Update action.yml Check dist/ #10: Commit b0ace84 pushed by agilebotanist
February 26, 2024 11:17 23s main
main
February 26, 2024 11:17 23s
v1.2 Check dist/ #9: Commit 71968a3 pushed by agilebotanist
February 26, 2024 11:11 28s main
main
February 26, 2024 11:11 28s
p Check dist/ #8: Commit d1b45f3 pushed by agilebotanist
February 26, 2024 11:10 26s main
main
February 26, 2024 11:10 26s
u Check dist/ #7: Commit f44f329 pushed by agilebotanist
February 26, 2024 11:08 28s main
main
February 26, 2024 11:08 28s
package Check dist/ #6: Commit 5245767 pushed by agilebotanist
February 26, 2024 11:06 18s main
main
February 26, 2024 11:06 18s
Update action.yml Check dist/ #5: Commit 8997ad3 pushed by agilebotanist
February 26, 2024 10:41 21s main
main
February 26, 2024 10:41 21s
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
false Check dist/ #4: Commit 5f28a85 pushed by agilebotanist
February 23, 2024 22:14 22s main
main
February 23, 2024 22:14 22s
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
required Check dist/ #3: Commit ca054b4 pushed by agilebotanist
February 23, 2024 22:11 22s main
main
February 23, 2024 22:11 22s
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
rq Check dist/ #2: Commit c224110 pushed by agilebotanist
February 23, 2024 22:07 23s main
main
February 23, 2024 22:07 23s
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
token for rqcode issues creation Check dist/ #1: Commit 57382aa pushed by agilebotanist
February 23, 2024 22:04 25s main
main
February 23, 2024 22:04 25s
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