YouTube2Text

Cyber Security Project Explanation Session|| Infotact Solutions — Transcript

by Infotact Solutions · 2,340 words · 366 segments · language en · Watch on YouTube

Full transcript

  1. 1:33Good evening team. So we are starting up
  2. 1:35with our uh audit explanation. So first
  3. 1:39of all let me share my screen as you
  4. 1:42might have received your uh document. So
  5. 1:45that document only I'll be sharing.
  6. 1:47Yeah. So accordingly one by one I will
  7. 1:49be explaining out the project. So you
  8. 1:51have total one two and three projects on
  9. 1:54the way and uh
  10. 1:58yeah so the first project is the world.
  11. 2:01So this project will be focusing on
  12. 2:03industrial control system ICS. Okay. Uh
  13. 2:07and the CAD server security. So unlike
  14. 2:10the traditional firewalls that one uh
  15. 2:12that only check whether the network uh
  16. 2:15packet is correctly formatted
  17. 2:17old guard also check whether the command
  18. 2:20is physically safe before allowing it to
  19. 2:23reach industrial equipment. Okay. So for
  20. 2:26example imagine a hacker sends a valid
  21. 2:28uh mod bus command telling a water pump
  22. 2:31to run at 50,000 RPM. A normal firewall
  23. 2:35may allow it because the packet is
  24. 2:37valid. Okay. The world guard to s uh
  25. 2:40simulates that what happened to the
  26. 2:43pipeline first. Okay. If it predicts the
  27. 2:46pipe will burst due to excessive
  28. 2:48pressure, it will block the command
  29. 2:50immediately. Okay. This is something
  30. 2:52like which will be uh used over into the
  31. 2:55system.
  32. 3:16Yes. So the problem statement over here
  33. 3:18is like uh industrial system like in uh
  34. 3:21power plants water treatment facilities
  35. 3:23the fac uh factories uses this protocol
  36. 3:26such as the mod bus or DNP3. Okay. So
  37. 3:29these all protocols often lack strong
  38. 3:31security. So an attacker can send uh
  39. 3:34legitimate looking commands that cause
  40. 3:36dangerous physical damage. Okay. So the
  41. 3:38objective over for this project is to
  42. 3:40stop such attacks by validating commands
  43. 3:43based on real world physics. Okay. not
  44. 3:45just network rules. Okay. So this is the
  45. 3:48background and here you will be building
  46. 3:51the packet interceptor and uh physics
  47. 3:54simulation engine and then decision
  48. 3:56engine and then uh operator dashboards
  49. 3:59will be there. Okay. So build an uh
  50. 4:02build a desktop application using C++
  51. 4:04and QT. Okay. where the plant will oper
  52. 4:08uh plant operator can monitor incoming
  53. 4:10commands and accordingly they can view
  54. 4:13blocked uh attackers and observe the
  55. 4:16graph showing system pressure and all
  56. 4:17those things. Okay.
  57. 4:26So by this you'll be using C++, Japa,
  58. 4:29Python, open model, rust or uh like for
  59. 4:34the desktop application you'll be using
  60. 4:35the C++ and QT. Okay, by this moving
  61. 4:40forward with the next project that is
  62. 4:42the
  63. 4:44eighth round.
  64. 4:47Okay, as the project is still here.
  65. 4:54So over here for this project
  66. 4:58what exactly we'll be doing it's a
  67. 5:00acostic covert channel detector okay as
  68. 5:03it is mentioned. So over here uh the
  69. 5:06project do focuses on the hardware cyber
  70. 5:09security and the signal uh intelligence.
  71. 5:11Okay the signet
  72. 5:13okay so goal is to detect the malware
  73. 5:16that steals data from air gap computers.
  74. 5:19Okay the system that are completely
  75. 5:21disconnected from the internet or
  76. 5:23something like that. Okay. Normally the
  77. 5:25air gap systems are considered very
  78. 5:27secure. Okay. However, advanced attacker
  79. 5:30can use malware to make the computer
  80. 5:33secretly transmit data through radio
  81. 5:36signals RF.
  82. 5:38Okay. Radio frequency you can say or uh
  83. 5:41the sound waves such as changing CPU fan
  84. 5:44speed or uh memory activity to encode
  85. 5:48the information
  86. 5:50or uh uh like that. Okay. Okay. So,
  87. 5:52Aether Hound is to be designed to detect
  88. 5:54these hidden transmissions.
  89. 5:56Okay. So, traditionally antivirus
  90. 5:58software monitor uh files like uh
  91. 6:01processes and network traffic. But if a
  92. 6:04computer is not having any network
  93. 6:07connection,
  94. 6:08attackers may use uh convert the
  95. 6:11communication channel like ultrasonic
  96. 6:13sound or the electromagnetic emissions
  97. 6:16to lag the sensitive data. Okay. So the
  98. 6:19objective over here we need to go up
  99. 6:21with to continuously monitor the
  100. 6:23environment around the server and
  101. 6:25identify any unusual RF or uh acostic
  102. 6:28plat uh patterns that indicate the data
  103. 6:31extra filtration. Okay. So for this you
  104. 6:33need to
  105. 6:35work on four main module. First the
  106. 6:37hardware monitoring system you need to
  107. 6:39set up uh uh like u means how an array
  108. 6:45of ultra sonic microphones like how it
  109. 6:48produces the sound and accordingly the
  110. 6:51sensor will be collecting out the data
  111. 6:53and that you'll be using okay signal
  112. 6:56processing pipeline the GNU radio and
  113. 6:58Python you'll be using to capture the RF
  114. 7:01okay and uh you'll be using the machine
  115. 7:04learning anomaly detector that you will
  116. 7:06be training training one uh autocoder
  117. 7:09neural networks and uh using the
  118. 7:12tensorflow okay or pytorch you can use
  119. 7:15on normal server room emissions okay
  120. 7:19whatever you want okay go up with the
  121. 7:21dummy data okay and monitoring interface
  122. 7:25that is required you need to build a
  123. 7:26terminal based dashboard CLI
  124. 7:29uh you can use the cursors okay the
  125. 7:32interface should be should display the
  126. 7:33live uh radio frequency spectrum
  127. 7:36activity
  128. 7:37and acostic signal levels, anomaly
  129. 7:39alerts and identify which server rack is
  130. 7:42producing suspicious emissions. Okay,
  131. 7:45that's the expectation.
  132. 7:47Okay.
  133. 7:49So over here if you go up with into like
  134. 7:52for this as in very much practical so
  135. 7:54you'll be needing one Raspberry Pi. If
  136. 7:57you don't have you can just use your
  137. 7:58laptop only. No issues on that. Okay.
  138. 8:01But if you if you want to create
  139. 8:04something like uh a really different so
  140. 8:06you can use that if you have okay uh
  141. 8:09Raspberry Pi hack RF software uh that
  142. 8:12will defining the radio or ultrasonic
  143. 8:14microphones okay eventually laptops to
  144. 8:17have that and uh accordingly
  145. 8:21go ahead with that okay
  146. 8:25so by this you are moving forward with
  147. 8:27the next project that is uh neuroence
  148. 8:36Okay.
  149. 9:09This is your third project that is the
  150. 9:10neuro fence. Okay.
  151. 9:16So this is particularly a project on
  152. 9:19which you will be like uh means uh uh
  153. 9:24you'll be checking whether the
  154. 9:25opensource LLMs are being secretly
  155. 9:27modified by the attackers before the
  156. 9:29organizations are deploying it or not.
  157. 9:32Okay. For example, an attacker may
  158. 9:34upload a poisoned AI model that behaves
  159. 9:36normally for everyday's question, but
  160. 9:39when it receives a uh secret trigger
  161. 9:42phase like deploy, override like that.
  162. 9:45So, it will start leaking the
  163. 9:46confidential information or generating
  164. 9:48malicious code. Okay. So, neuroence is
  165. 9:51designed to detect this hiddens uh
  166. 9:54hidden back doors before the model is
  167. 9:56used. Okay. So many companies do
  168. 9:58download open-source uh AI models from
  169. 10:01the internet while the models may appear
  170. 10:04to work correctly. Okay. The attackers
  171. 10:06can hide the back doors inside the model
  172. 10:09waste and these backd doors to remain
  173. 10:12inactive during normal use and only
  174. 10:14active when specific trigger prompts are
  175. 10:16given. Okay. The objective over here is
  176. 10:19to analyze the model offline and
  177. 10:21identify suspicious
  178. 10:23uh hidden behavior of it. Okay. So the
  179. 10:26project will be there for four major
  180. 10:29modules. Okay. Uh first the model
  181. 10:32sandbox means it will you need to create
  182. 10:34a secure environment using PyTorch and
  183. 10:36hugging face to load the uh to load
  184. 10:39downloaded LLM safely and the model
  185. 10:42should be isolated so that uh loading it
  186. 10:45cannot execute any untrusted code. Okay.
  187. 10:48and advancial prompt generator will be
  188. 10:50you need to develop an activation
  189. 10:52analysis engine using the PyTorch uh
  190. 10:55hooks and for desktop application you'll
  191. 10:58be building an offline uh desktop
  192. 11:00application using electron and uh IQT
  193. 11:03okay and uh yeah that's all so you'll be
  194. 11:08mainly using PyTorch hugging face
  195. 11:09transformers Python PyTorch hooks
  196. 11:12electron or pyq okay so these are all
  197. 11:16the three projects that we'll be going
  198. 11:18ahead. So before going up with your
  199. 11:20queries, I'll be telling you two things.
  200. 11:22First, you need to adhere with the
  201. 11:24GitHub policy. You need to connect your
  202. 11:26GitHub repository with uh with our
  203. 11:28dashboard. Okay? And accordingly, each
  204. 11:30of the team members
  205. 11:32will be creating their branch in the
  206. 11:35repository. Okay? And accordingly you
  207. 11:37will be working onto your branch. So if
  208. 11:40team member is consisting of four
  209. 11:42member, so four branch plus one
  210. 11:44production branch you will be creating.
  211. 11:46production branch will be checked uh for
  212. 11:48the output. Okay. And the other four
  213. 11:52branches will be there for uh
  214. 11:55your contributions. Okay. And
  215. 11:57accordingly you will be
  216. 12:20All right. And one more thing is like
  217. 12:22you'll be working in a team and
  218. 12:24accordingly uh your trainers will be
  219. 12:26training you guys for the uh text that
  220. 12:28is there. And if you have any type of
  221. 12:29queries related to the uh project, you
  222. 12:31are not supposed to disclose the project
  223. 12:34to your trainer or anyone okay outside
  224. 12:37the firm. So you need to uh means ask
  225. 12:40the specific doubt or query to them.
  226. 12:42Okay, that's what it is expected and
  227. 12:44accordingly your submission will be done
  228. 12:46that will the dates will be flashing or
  229. 12:48it will be flashed when it is decided by
  230. 12:50the code team in the dashboard. Okay.
  231. 12:53And according to the norms you will be
  232. 12:55going ahead with that. Okay. So
  233. 12:59yeah and one more thing is like if you
  234. 13:01are exhausted with your project let's
  235. 13:02say if uh the maximum timeline for one
  236. 13:04project is four weeks week 1 week 2 week
  237. 13:07three and week four. Say if you have
  238. 13:10completed uh this particular project
  239. 13:12within week three only. So you're not
  240. 13:14supposed to see title for week four.
  241. 13:16Okay. You'll be starting with your
  242. 13:18project two directly. Okay. So there
  243. 13:20will be no spoon feeding over here. You
  244. 13:22need to mind the things accordingly. You
  245. 13:24need to uh
  246. 13:28uh means uh get the ownership for your
  247. 13:30project. Okay. And accordingly go ahead
  248. 13:33with it. Okay. This all are production
  249. 13:35ready project, production level project.
  250. 13:37So our team is also working and
  251. 13:39accordingly you will also work. So your
  252. 13:40work will be evaluated and validated by
  253. 13:43the production team. So uh give you a
  254. 13:46based on it. Okay. And if you have any
  255. 13:49doubt or query, I'll be opening the chat
  256. 13:51section for 5 minutes. Okay. Put your
  257. 13:54doubts or query over in the chat. After
  258. 13:565 minutes, we'll be I'll be answering
  259. 13:58all of your doubts. So it is 58. So we
  260. 14:01will be
  261. 14:04uh discussing with your doubt by 75.
  262. 14:07Okay. So by 7 sorry uh by 85. Okay. So
  263. 14:12till then please put your doubts and
  264. 14:14query over in the chat.
  265. 21:29All right. So we had received the
  266. 21:32queries. So I have to ask that two
  267. 21:34months internship program. This is
  268. 21:36compulsory to make three projects. The
  269. 21:39offer is yeah the offer if it is asks to
  270. 21:43make two. So that is the minimum
  271. 21:45requirement. Okay. If you can mean you
  272. 21:48need to develop too. Okay. And
  273. 21:52accordingly you can process. Okay.
  274. 21:55Uh can we use AI? Yes, of course you can
  275. 21:57use AI but uh my recommendation is do
  276. 22:00not fully depend over on AI so that you
  277. 22:03will not be learning the things
  278. 22:05properly. Okay.
  279. 22:07Or can you just send these all things in
  280. 22:09text like related project? Yes. this
  281. 22:12project details and the document is
  282. 22:14already being shared onto your common
  283. 22:16group. So there you can check it on and
  284. 22:18again I'll be uh taking uh uh means
  285. 22:22asking the team to share the project
  286. 22:24details again. Okay.
  287. 22:27Software requirement I have discussed
  288. 22:29the software requirement over here what
  289. 22:31you will be using. Okay. Do you have to
  290. 22:34do two or three project on all three?
  291. 22:36All three is minimum. Okay. If you have
  292. 22:39if you if you will complete the three
  293. 22:41projects and if you are exhausted with
  294. 22:43your project you need to report it to
  295. 22:44your manager. Your manager will be
  296. 22:46providing you the next sort of projects.
  297. 22:47Okay. What if sir I complete project
  298. 22:51before week four. So if you complete
  299. 22:53before week four as I've already told
  300. 22:55you to continue start with your next
  301. 22:58project. Okay. Do not hold or wait for
  302. 23:02the same. Okay.
  303. 23:05is your dashboard. We want to connect
  304. 23:07with old GitHub project or the company
  305. 23:09GitHub project.
  306. 23:12You need to uh connect with your uh
  307. 23:16repository that is there. Okay. For
  308. 23:19which uh on which you'll be creating the
  309. 23:22uh
  310. 23:24uh application. Okay.
  311. 25:25All right. So the next is we need to do
  312. 25:27two out of three. Fine. We have already
  313. 25:30given what complete user dashboard we
  314. 25:35want connect old GitHub project. No no
  315. 25:38if for one project you will be
  316. 25:40connecting your one repository and
  317. 25:41accordingly what is your branch you will
  318. 25:44be connecting that. So everyone will be
  319. 25:46working onto their branch and you need
  320. 25:48to connect your branch onto the
  321. 25:50dashboard. Okay. Security domain we will
  322. 25:53be guided training on tools. Yes, you'll
  323. 25:55be guided over onto the tools
  324. 25:57accordingly.
  325. 25:59Trainings are all provided by Intel and
  326. 26:01they will be providing it to you. Okay,
  327. 26:03don't worry.
  328. 26:07Friend also in cyers she received her
  329. 26:10coupon code for certification code. When
  330. 26:14did I receive sir? It is on your third
  331. 26:16month. On your third month, you can just
  332. 26:18ask with your manager. They will be
  333. 26:20sharing that. Okay. Is it necessary to
  334. 26:24complete the course that is provided by
  335. 26:27the company?
  336. 26:29It is not any course or something. You
  337. 26:31need to you are in a internship. You'll
  338. 26:33be creating the softwares or uh the
  339. 26:36requirement according the what we have
  340. 26:37discussed.
  341. 26:48So if a project is like uh means what
  342. 26:53that I have just shared okay the last
  343. 26:55question that I'm explaining
  344. 26:58let's say the week wise if you check the
  345. 27:02week uh uh building thing okay here so
  346. 27:06everyone these all things everyone needs
  347. 27:08to do okay So everyone will be doing
  348. 27:11collaboratively and accordingly you will
  349. 27:13be going ahead with that. Someone will
  350. 27:15be creating the DSP flow graph. Someone
  351. 27:18will be get uh working on to the past
  352. 27:21four year transfer FFTs. Someone will be
  353. 27:23working on conversion of audio RF into
  354. 27:25specttogram matrix. Like that you will
  355. 27:27be dividing your work. Okay.
  356. 27:31Like this only.
  357. 27:36Okay.
  358. 27:43Stop.
  359. 27:59Sorry.
  360. 28:14I hope uh it's fine and now we are going
  361. 28:17forward to
  362. 28:22it. Thank you so much as
  363. 28:27we have completed three. I hope everyone
  364. 28:29have understood how to work with that.
  365. 28:37All right, fine. Thank you. You may now
  366. 28:39drop off from this car.

About this transcript

This page contains the full transcript of Cyber Security Project Explanation Session|| Infotact Solutions by Infotact Solutions, generated from the public captions YouTube serves with the video. The transcript has 2,340 words across 366 segments, with the original timestamps preserved so you can click any line to jump to that moment in the embedded player.

What you can do with it

Use the transcript to take notes, quote the speaker, build a study guide, generate a summary with ChatGPT or Claude via the YouTube Summary tool, or export it as a timed subtitle file with YouTube to SRT. You can also re-open it in the transcriber to translate the transcript into 100+ languages.

Free YouTube transcript tool

YouTube2Text is a free YouTube transcript generator — no signup, no daily limit. Paste any YouTube link and get the full transcript instantly, with timestamps, click-to-jump, translation to 100+ languages, AI prompts for ChatGPT, Claude, and Gemini, and exports to TXT, SRT, VTT, or Markdown.