-
Notifications
You must be signed in to change notification settings - Fork 0
Issue Template
michschl edited this page Nov 19, 2024
·
1 revision
[Provide a detailed description of the task, including objectives and context, referencing specific standards, profiles, or documentation where necessary.]
The task is considered complete when:
- [Measurable criteria that need to be met for this task to be considered done.]
- [Measurable criteria that need to be met for this task to be considered done.]
- [List any dependencies, such as other tasks, approvals, or required input from stakeholders.]
- Assignee: [Person responsible for completing this task]
- Contributer(s): [List the person(s) who support to complete this task]
- Reviewer(s): [List the person(s) responsible for reviewing this task]
- [Link to relevant profiles, standards, guidelines, or other reference materials]
- [Any additional notes, context, or relevant details]
- Initial Review Date: [Scheduled date for first review or check-in]
- Next Meeting Goal: Ensure the task is on track to be presented in the next stream meeting.
- Scope is Defined: The task aligns with stream objectives and has a clear scope.
- Acceptance Criteria: Acceptance criteria are clear, specific, and measurable.
- Dependencies and Stakeholders: Necessary dependencies and stakeholders are identified.
- Technical Requirements: Relevant technical details and resources are available.
SFTI | ca-security
Wiki
API Security & Consent Management
- Foundations and assumptions
- Basic API Security Principles
- FAPI 2.0 Swiss Security Profile
- Consent Management
- Implementation example Multibanking
- Strong Customer Authentication (SCA)
- Glossary and terminology
Version Management
Implementation Guidelines