• Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • None
    • False
    • None
    • False
    • SECFLOWOTL-30 - s2i Security Review

      Use the following guidelines for centralizing authorization:

      • Centralize authorization into a single module, layer, or location.
        - All views, application programming interfaces (APIs), and other interfaces should pass through the same security code to ensure authorization is consistent.
        
      • Avoid hard-coding authorization logic into the presentation layers, especially for web applications.
        - This makes authorization maintenance more complex and inconsistent because it leads to a risk of duplicating authorization features.
        - In certain conditions, attackers can exploit these inconsistencies and bypass authorization checks entirely.
        

      Imported from SD Elements: https://redhat.sdelements.com/bunits/psse-secure-development/group-2-extended-functionality-offerings/openshift-source-to-image-s2i-builder-image/tasks/phase/architecture-design/106-T15/

              gkamathe@redhat.com Gaurav Kamathe
              sdelements Jira-SD-Elements-Integration Bot
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: