To entirely remove unwanted files from a repository ' s history you can use either the git filter-branch command or the BFG Repo-Cleaner open source tool.
Reference:
https://docs.github.com/en/github/authenticating-to-github/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository

See explanation below
Explanation:
Task 7: Create a Pipeline to Deploy a Docker Image in a New Branch
Step 1: Create a New Branch
* In your Azure DevOps Project (Project1), navigate to Repos .
* In the left menu, click on Branches .
* Click New branch .
* Enter:
* Branch name: azure-pipelines
* Based on: main (or your default branch)
* Click Create .
This creates a new branch named azure-pipelines.
Step 2: Switch to the New Branch
* In Repos , click on Files .
* In the top-left branch selector, choose azure-pipelines .
Step 3: Use the Predefined Docker Pipeline Template
Azure Pipelines has predefined YAML templates for common tasks, including Docker.
Here's how to add it:
* In the azure-pipelines branch, click New file .
* Name the file: azure-pipelines.yml.
* Click the Show templates button in the YAML editor (if available).
* Search for the Docker template in the list of predefined templates.
* Select the Docker template to auto-populate the YAML file.
If the editor doesn't show the template picker, you can manually add the following basic Docker pipeline template:
yaml
Copy
# Predefined Docker pipeline template
trigger:
- main
resources:
- repo: self
variables:
imageName: ' mydockerimage '
stages:
- stage: Build
displayName: Build and push stage
jobs:
- job: Build
pool:
vmImage: ' ubuntu-latest '
steps:
- task: Docker@2
displayName: Build and push an image to container registry
inputs:
command: buildAndPush
repository: $(imageName)
dockerfile: ' **/Dockerfile '
containerRegistry: ' < your-container-registry-service-connection > '
tags: |
latest
Replace < your-container-registry-service-connection > with your actual Azure Container Registry (ACR) or DockerHub service connection name.
Step 4: Commit the Pipeline to the New Branch
* In the YAML editor, review and adjust if needed (like setting the correct container registry service connection).
* In the bottom commit message box:
* Message: e.g., Add Docker deployment pipeline
* Ensure the branch is set to azure-pipelines .
* Click Commit (not commit to main).
This creates the pipeline YAML file in the new azure-pipelines branch.
Step 5: Create the Pipeline in Azure DevOps
* In the left menu, click Pipelines .
* Click New pipeline .
* Choose:
* Azure Repos Git .
* Select your repo.
* Select Existing Azure Pipelines YAML file .
* In the branch selector, choose the azure-pipelines branch.
* Select the YAML file path (azure-pipelines.yml).
* Click Continue and then Run to validate the pipeline.

The basic idea behind Continuous Assurance (CA) is to setup the ability to check for " drift " from what is considered a secure snapshot of a system. Support for Continuous Assurance lets us treat security truly as a ' state ' as opposed to a ' point in time ' achievement. This is particularly important in today ' s context when ' continuous change ' has become a norm.
There can be two types of drift:
* Drift involving ' baseline ' configuration: This involves settings that have a fixed number of possible states (often pre-defined/statically determined ones). For instance, a SQL DB can have TDE encryption turned ON or OFF...or a Storage Account may have auditing turned ON however the log retention period may be less than 365 days.
* Drift involving ' stateful ' configuration: There are settings which cannot be constrained within a finite set of well-known states. For instance, the IP addresses configured to have access to a SQL DB can be any (arbitrary) set of IP addresses. In such scenarios, usually human judgment is initially required to determine whether a particular configuration should be considered ' secure ' or not. However, once that is done, it is important to ensure that there is no " stateful drift " from the attested configuration. (E.g., if, in a troubleshooting session, someone adds the IP address of a developer machine to the list, the Continuous Assurance feature should be able to identify the drift and generate notifications/alerts or even trigger ' auto-remediation ' depending on the severity of the change).
Reference:
https://azsk.azurewebsites.net/04-Contin ous-Assurance/Readme.htm l

See the solution below in explanation.
Explanation:
Step 1: Create a Project Wiki
Navigate to Azure DevOps:
Go to Azure DevOps and sign inwith your credentials.
Select Your Project:
Choose Project1 from your list of projects.
Create a Wiki:
In the left-hand menu, select Wiki.
Click on Create project wiki.
Enter the name Wiki1 and click Create.
Step 2: Add Mermaid Syntax to Render a Diagram
Open the Wiki Page:
Navigate to the newly created Wiki1.
Edit the Wiki Page:
Click on Edit to start editing the wiki page.
Insert Mermaid Diagram:
Use the following Mermaid syntax to render a diagram. For example, to render a simple flowchart, you canuse:
```mermaid
graph TD;
A-- > B;
A-- > C;
B-- > D;
C-- > D;
Save the Page:
Click on Save to save your changes.
Step 3: Render the TCP Handshake Diagram
Convert TCPHandshake.png to Mermaid Syntax:
Since you have a sample diagram in C:\Resources\TCPHandshake.png, you need to convert this diagram into Mermaid syntax. Here's an example of how a TCP handshake might look in Mermaid syntax:
```mermaid
sequenceDiagram
participant Client
participant Server
Client- > > Server: SYN
Server-- > > Client: SYN-ACK
Client- > > Server: ACK
Add the Diagram to the Wiki:
Replace the sample Mermaid syntax with the TCP handshake diagram syntax in the wiki page.
Save the Page:
Click on Save to save your changes.
By following these steps, you will have created a project wiki named Wiki1 and used Mermaid syntax to render a diagram

WhiteSource provides WhiteSource Bolt, a lightweight open source security and management solution developed specifically for integration with Azure DevOps and Azure DevOps Server.
Note: WhiteSource is the leader in continuous open source software security and compliance management.
WhiteSource integratesinto your build process, irrespective of your programming languages, build tools, or development environments. It works automatically, continuously, and silently in the background, checking the security, licensing, and quality of your open source components against WhiteSource constantly-updated de#nitive database of open source repositories.
Note: Blackduck would also be a good answer, but it is not an option here.
Reference:
https://www.azuredevopslabs.com/labs/vstsextend/whitesource/