Various Techniques and Processes within Scrum?

What this means is that you can employ pretty much whatever process that your team wants to use. They can use Pair Programming, TDD, Kanban, etc etc. In other words, if your team has been using a Kanban board and limits for each column, they can use that in the Scrum Framework.

I've seen many Extreme Programming practices go well within the Scrum framework: the planning game (adding release planning on top of the Sprint Planning, which covers XP's iteration planning) user stories, story point estimation, test-driven development, behavior-driven development, pair programming, continuous integration, coding standards (especially as part of the Definition of Done).

Of course, there are other practices. Most of Scrum says what you need to do, not how you need to do it. There are various techniques for running effective Daily Scrums, Sprint Reviews, Sprint Retrospectives, and the general day-to-day activities of the Development Team. Many of these fit perfectly within the Scrum framework, even though they aren't part of Scrum.

Kindly enlighten me on the various processes and techniques which can be followed as a part of scrum. 

The Professional Scrum Developer course gives a window onto some of these, such as TDD and CI/CD, DevOps, ALM and pairing.

It is important to keep in mind that Scrum is built on empiricism.

If an organization, team or individual decide to add something on top of Scrum, it is important to be transparent about it, and regularly inspect and adapt, to make sure that this additional practice is helping.