SPIKE: To investigate SmartConsole User Authentication options

[bruce-wh-li]

Describe the Issue As firewall admin, I would like to find out how to authenticate smartconsole user other than on promise RADIUS server running on Networking Device.

Additional Context

• Find out from Chris C. or Michael V. the RADIUS info (IP Address, SPAN, NAT address, Idp, MFA )
• Check with ES any RADIUS server running on NPS in cloud that can be used by cloud firewall
• Check with Firewall Vendor for best practice and recommendation

Acceptance Criteria

• [ ] On premise radius server information (IP Address, port number, NAT, Transit Gateway and so on)
• [ ] Tacacs+, Radius Server running in cloud
• [ ] Checkpoint TAC Support Feedback
• [ ] Review w/ the team

Definition of Ready These set of conditions will need to be met in order to bring a ticket into the sprint and start work. Protects the team from unclear requirements. Issues (Task/Story/Spike) aligned to an EPIC and linked appropriately. Assigned to the appropriate CPF MEMBER (and is not left blank in ZenHub) at the start of sprint (1st day of the sprint) Acceptance has been defined for the issue and has been reviewed with CPF team and approved by the necessary approver. Has been sized and estimated by the delivery team. Detailed breakdown of the steps required to complete the story in the additional context Any additional specifications have been documented, reviewed with CPF and approved by the necessary approver.

Acceptance Criteria A set of pre-defined requirement that need to be met in order to mark the user story as “done”. It should be testable with no room for interpretation It should be either “pass” or “fail” It should be clear enough for business stake holders to understand As part of the user story, it should be written from the user perspective A well written acceptance criteria is great for

• managing expectations
• defining scope
• reducing ambiguity
• establishing testing criteria for QA Given (Pre-condition) When (Action) Then (Outcome)

Definition of Done These set of conditions are met for work to be considered as complete on an issue. All acceptance criteria(s) have been validated. All the necessary documentation for the issue has been uploaded to Teams. Functionality has been tested when applicable. Functionality has been demonstrated to the relevant stakeholders (where applicable). Story has been scheduled for a Sprint Demo/community update and impacted teams invited to the Demo. Stories accepted by PO and documented for potential sharing with impacted users.

• Documented = Captured in Community Update (CU) deck
• Release notes = aspirational goal of providing a bulleted list of features and changes that our users can touch. Was going to store them in our Cloud Pathfinder repo. Can also display to users in the CU

[bruce-wh-li]

The following are the options that I can think of:

1. On premise Radius/TACACs+ 2.Azure NPS/NAC 3.SAML through Azure AD
   4.Radius/Tacacs+ SaaS solution

Chris C. and Michael V. not Available until Aug.

[bruce-wh-li]

We have discussed and conclude that we will wait until direct connect (equinix) in prior to considering using RADIUS, TACACs+ for Authentication. However, a ticket for PoC to confirm feasibility to use simple SAML to authenticate firewall admin will be created.

[bruce-wh-li]

SAML authentication using idp, e.g. azure AD required CheckPoint R81.2.