Security declaration separate to course?

We've recently implemented a slide that requires learners to acknowledge it before they can continue to the subsequent slide, that subsequent slide being the one that actually sends completion to the LMS. Your idea for separating them would not be dissimilar, simply sending completion for the declaration module separate from the preceding content module.

Ours works with a Short Answer survey slide in Storyline. The textbox of the survey slide is where the learner enters their name, and then this trigger runs when the learner clicks the Submit (acknowledgement) button:

Good UX of course necessitates a few more triggers for visual assets, including one that gives the input text box a red border if someone clicks the Submit button without entering anything in the text box.

Since the text box is a survey field, it's then sent to the LMS where reports can be pulled to show when someone acknowledged the relevant policy as well as what they actually entered.

As icing on the cake, the slide uses JavaScript to query Workday LMS for the learner's first and last names, and then puts them into a variable shown on the screen in the declaration text. ("I, Nadine Britton, have read and understood...") Our thinking is that people take declarations more seriously if the declaration already seems to know their name.