├── .github └── FUNDING.yml ├── LICENSE ├── README.md └── scripts ├── .gitignore ├── kube-bench-scan.pdf ├── kube-bench-scan.txt ├── kube-bench.sh ├── kube-hunter-scan.pdf ├── kube-hunter-scan.txt ├── kube-hunter.sh ├── marvin-scan.txt ├── marvin.sh ├── popeye.sh └── report.html /.github/FUNDING.yml: -------------------------------------------------------------------------------- 1 | # These are supported funding model platforms 2 | 3 | github: nataliagranato 4 | ko_fi: nataliagranato 5 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | GNU GENERAL PUBLIC LICENSE 2 | Version 3, 29 June 2007 3 | 4 | Copyright (C) 2007 Free Software Foundation, Inc. 5 | Everyone is permitted to copy and distribute verbatim copies 6 | of this license document, but changing it is not allowed. 7 | 8 | Preamble 9 | 10 | The GNU General Public License is a free, copyleft license for 11 | software and other kinds of works. 12 | 13 | The licenses for most software and other practical works are designed 14 | to take away your freedom to share and change the works. By contrast, 15 | the GNU General Public License is intended to guarantee your freedom to 16 | share and change all versions of a program--to make sure it remains free 17 | software for all its users. We, the Free Software Foundation, use the 18 | GNU General Public License for most of our software; it applies also to 19 | any other work released this way by its authors. You can apply it to 20 | your programs, too. 21 | 22 | When we speak of free software, we are referring to freedom, not 23 | price. Our General Public Licenses are designed to make sure that you 24 | have the freedom to distribute copies of free software (and charge for 25 | them if you wish), that you receive source code or can get it if you 26 | want it, that you can change the software or use pieces of it in new 27 | free programs, and that you know you can do these things. 28 | 29 | To protect your rights, we need to prevent others from denying you 30 | these rights or asking you to surrender the rights. Therefore, you have 31 | certain responsibilities if you distribute copies of the software, or if 32 | you modify it: responsibilities to respect the freedom of others. 33 | 34 | For example, if you distribute copies of such a program, whether 35 | gratis or for a fee, you must pass on to the recipients the same 36 | freedoms that you received. You must make sure that they, too, receive 37 | or can get the source code. And you must show them these terms so they 38 | know their rights. 39 | 40 | Developers that use the GNU GPL protect your rights with two steps: 41 | (1) assert copyright on the software, and (2) offer you this License 42 | giving you legal permission to copy, distribute and/or modify it. 43 | 44 | For the developers' and authors' protection, the GPL clearly explains 45 | that there is no warranty for this free software. For both users' and 46 | authors' sake, the GPL requires that modified versions be marked as 47 | changed, so that their problems will not be attributed erroneously to 48 | authors of previous versions. 49 | 50 | Some devices are designed to deny users access to install or run 51 | modified versions of the software inside them, although the manufacturer 52 | can do so. This is fundamentally incompatible with the aim of 53 | protecting users' freedom to change the software. The systematic 54 | pattern of such abuse occurs in the area of products for individuals to 55 | use, which is precisely where it is most unacceptable. Therefore, we 56 | have designed this version of the GPL to prohibit the practice for those 57 | products. If such problems arise substantially in other domains, we 58 | stand ready to extend this provision to those domains in future versions 59 | of the GPL, as needed to protect the freedom of users. 60 | 61 | Finally, every program is threatened constantly by software patents. 62 | States should not allow patents to restrict development and use of 63 | software on general-purpose computers, but in those that do, we wish to 64 | avoid the special danger that patents applied to a free program could 65 | make it effectively proprietary. To prevent this, the GPL assures that 66 | patents cannot be used to render the program non-free. 67 | 68 | The precise terms and conditions for copying, distribution and 69 | modification follow. 70 | 71 | TERMS AND CONDITIONS 72 | 73 | 0. Definitions. 74 | 75 | "This License" refers to version 3 of the GNU General Public License. 76 | 77 | "Copyright" also means copyright-like laws that apply to other kinds of 78 | works, such as semiconductor masks. 79 | 80 | "The Program" refers to any copyrightable work licensed under this 81 | License. Each licensee is addressed as "you". "Licensees" and 82 | "recipients" may be individuals or organizations. 83 | 84 | To "modify" a work means to copy from or adapt all or part of the work 85 | in a fashion requiring copyright permission, other than the making of an 86 | exact copy. The resulting work is called a "modified version" of the 87 | earlier work or a work "based on" the earlier work. 88 | 89 | A "covered work" means either the unmodified Program or a work based 90 | on the Program. 91 | 92 | To "propagate" a work means to do anything with it that, without 93 | permission, would make you directly or secondarily liable for 94 | infringement under applicable copyright law, except executing it on a 95 | computer or modifying a private copy. Propagation includes copying, 96 | distribution (with or without modification), making available to the 97 | public, and in some countries other activities as well. 98 | 99 | To "convey" a work means any kind of propagation that enables other 100 | parties to make or receive copies. Mere interaction with a user through 101 | a computer network, with no transfer of a copy, is not conveying. 102 | 103 | An interactive user interface displays "Appropriate Legal Notices" 104 | to the extent that it includes a convenient and prominently visible 105 | feature that (1) displays an appropriate copyright notice, and (2) 106 | tells the user that there is no warranty for the work (except to the 107 | extent that warranties are provided), that licensees may convey the 108 | work under this License, and how to view a copy of this License. If 109 | the interface presents a list of user commands or options, such as a 110 | menu, a prominent item in the list meets this criterion. 111 | 112 | 1. Source Code. 113 | 114 | The "source code" for a work means the preferred form of the work 115 | for making modifications to it. "Object code" means any non-source 116 | form of a work. 117 | 118 | A "Standard Interface" means an interface that either is an official 119 | standard defined by a recognized standards body, or, in the case of 120 | interfaces specified for a particular programming language, one that 121 | is widely used among developers working in that language. 122 | 123 | The "System Libraries" of an executable work include anything, other 124 | than the work as a whole, that (a) is included in the normal form of 125 | packaging a Major Component, but which is not part of that Major 126 | Component, and (b) serves only to enable use of the work with that 127 | Major Component, or to implement a Standard Interface for which an 128 | implementation is available to the public in source code form. A 129 | "Major Component", in this context, means a major essential component 130 | (kernel, window system, and so on) of the specific operating system 131 | (if any) on which the executable work runs, or a compiler used to 132 | produce the work, or an object code interpreter used to run it. 133 | 134 | The "Corresponding Source" for a work in object code form means all 135 | the source code needed to generate, install, and (for an executable 136 | work) run the object code and to modify the work, including scripts to 137 | control those activities. However, it does not include the work's 138 | System Libraries, or general-purpose tools or generally available free 139 | programs which are used unmodified in performing those activities but 140 | which are not part of the work. For example, Corresponding Source 141 | includes interface definition files associated with source files for 142 | the work, and the source code for shared libraries and dynamically 143 | linked subprograms that the work is specifically designed to require, 144 | such as by intimate data communication or control flow between those 145 | subprograms and other parts of the work. 146 | 147 | The Corresponding Source need not include anything that users 148 | can regenerate automatically from other parts of the Corresponding 149 | Source. 150 | 151 | The Corresponding Source for a work in source code form is that 152 | same work. 153 | 154 | 2. Basic Permissions. 155 | 156 | All rights granted under this License are granted for the term of 157 | copyright on the Program, and are irrevocable provided the stated 158 | conditions are met. This License explicitly affirms your unlimited 159 | permission to run the unmodified Program. The output from running a 160 | covered work is covered by this License only if the output, given its 161 | content, constitutes a covered work. This License acknowledges your 162 | rights of fair use or other equivalent, as provided by copyright law. 163 | 164 | You may make, run and propagate covered works that you do not 165 | convey, without conditions so long as your license otherwise remains 166 | in force. You may convey covered works to others for the sole purpose 167 | of having them make modifications exclusively for you, or provide you 168 | with facilities for running those works, provided that you comply with 169 | the terms of this License in conveying all material for which you do 170 | not control copyright. Those thus making or running the covered works 171 | for you must do so exclusively on your behalf, under your direction 172 | and control, on terms that prohibit them from making any copies of 173 | your copyrighted material outside their relationship with you. 174 | 175 | Conveying under any other circumstances is permitted solely under 176 | the conditions stated below. Sublicensing is not allowed; section 10 177 | makes it unnecessary. 178 | 179 | 3. Protecting Users' Legal Rights From Anti-Circumvention Law. 180 | 181 | No covered work shall be deemed part of an effective technological 182 | measure under any applicable law fulfilling obligations under article 183 | 11 of the WIPO copyright treaty adopted on 20 December 1996, or 184 | similar laws prohibiting or restricting circumvention of such 185 | measures. 186 | 187 | When you convey a covered work, you waive any legal power to forbid 188 | circumvention of technological measures to the extent such circumvention 189 | is effected by exercising rights under this License with respect to 190 | the covered work, and you disclaim any intention to limit operation or 191 | modification of the work as a means of enforcing, against the work's 192 | users, your or third parties' legal rights to forbid circumvention of 193 | technological measures. 194 | 195 | 4. Conveying Verbatim Copies. 196 | 197 | You may convey verbatim copies of the Program's source code as you 198 | receive it, in any medium, provided that you conspicuously and 199 | appropriately publish on each copy an appropriate copyright notice; 200 | keep intact all notices stating that this License and any 201 | non-permissive terms added in accord with section 7 apply to the code; 202 | keep intact all notices of the absence of any warranty; and give all 203 | recipients a copy of this License along with the Program. 204 | 205 | You may charge any price or no price for each copy that you convey, 206 | and you may offer support or warranty protection for a fee. 207 | 208 | 5. Conveying Modified Source Versions. 209 | 210 | You may convey a work based on the Program, or the modifications to 211 | produce it from the Program, in the form of source code under the 212 | terms of section 4, provided that you also meet all of these conditions: 213 | 214 | a) The work must carry prominent notices stating that you modified 215 | it, and giving a relevant date. 216 | 217 | b) The work must carry prominent notices stating that it is 218 | released under this License and any conditions added under section 219 | 7. This requirement modifies the requirement in section 4 to 220 | "keep intact all notices". 221 | 222 | c) You must license the entire work, as a whole, under this 223 | License to anyone who comes into possession of a copy. This 224 | License will therefore apply, along with any applicable section 7 225 | additional terms, to the whole of the work, and all its parts, 226 | regardless of how they are packaged. This License gives no 227 | permission to license the work in any other way, but it does not 228 | invalidate such permission if you have separately received it. 229 | 230 | d) If the work has interactive user interfaces, each must display 231 | Appropriate Legal Notices; however, if the Program has interactive 232 | interfaces that do not display Appropriate Legal Notices, your 233 | work need not make them do so. 234 | 235 | A compilation of a covered work with other separate and independent 236 | works, which are not by their nature extensions of the covered work, 237 | and which are not combined with it such as to form a larger program, 238 | in or on a volume of a storage or distribution medium, is called an 239 | "aggregate" if the compilation and its resulting copyright are not 240 | used to limit the access or legal rights of the compilation's users 241 | beyond what the individual works permit. Inclusion of a covered work 242 | in an aggregate does not cause this License to apply to the other 243 | parts of the aggregate. 244 | 245 | 6. Conveying Non-Source Forms. 246 | 247 | You may convey a covered work in object code form under the terms 248 | of sections 4 and 5, provided that you also convey the 249 | machine-readable Corresponding Source under the terms of this License, 250 | in one of these ways: 251 | 252 | a) Convey the object code in, or embodied in, a physical product 253 | (including a physical distribution medium), accompanied by the 254 | Corresponding Source fixed on a durable physical medium 255 | customarily used for software interchange. 256 | 257 | b) Convey the object code in, or embodied in, a physical product 258 | (including a physical distribution medium), accompanied by a 259 | written offer, valid for at least three years and valid for as 260 | long as you offer spare parts or customer support for that product 261 | model, to give anyone who possesses the object code either (1) a 262 | copy of the Corresponding Source for all the software in the 263 | product that is covered by this License, on a durable physical 264 | medium customarily used for software interchange, for a price no 265 | more than your reasonable cost of physically performing this 266 | conveying of source, or (2) access to copy the 267 | Corresponding Source from a network server at no charge. 268 | 269 | c) Convey individual copies of the object code with a copy of the 270 | written offer to provide the Corresponding Source. This 271 | alternative is allowed only occasionally and noncommercially, and 272 | only if you received the object code with such an offer, in accord 273 | with subsection 6b. 274 | 275 | d) Convey the object code by offering access from a designated 276 | place (gratis or for a charge), and offer equivalent access to the 277 | Corresponding Source in the same way through the same place at no 278 | further charge. You need not require recipients to copy the 279 | Corresponding Source along with the object code. If the place to 280 | copy the object code is a network server, the Corresponding Source 281 | may be on a different server (operated by you or a third party) 282 | that supports equivalent copying facilities, provided you maintain 283 | clear directions next to the object code saying where to find the 284 | Corresponding Source. Regardless of what server hosts the 285 | Corresponding Source, you remain obligated to ensure that it is 286 | available for as long as needed to satisfy these requirements. 287 | 288 | e) Convey the object code using peer-to-peer transmission, provided 289 | you inform other peers where the object code and Corresponding 290 | Source of the work are being offered to the general public at no 291 | charge under subsection 6d. 292 | 293 | A separable portion of the object code, whose source code is excluded 294 | from the Corresponding Source as a System Library, need not be 295 | included in conveying the object code work. 296 | 297 | A "User Product" is either (1) a "consumer product", which means any 298 | tangible personal property which is normally used for personal, family, 299 | or household purposes, or (2) anything designed or sold for incorporation 300 | into a dwelling. In determining whether a product is a consumer product, 301 | doubtful cases shall be resolved in favor of coverage. For a particular 302 | product received by a particular user, "normally used" refers to a 303 | typical or common use of that class of product, regardless of the status 304 | of the particular user or of the way in which the particular user 305 | actually uses, or expects or is expected to use, the product. A product 306 | is a consumer product regardless of whether the product has substantial 307 | commercial, industrial or non-consumer uses, unless such uses represent 308 | the only significant mode of use of the product. 309 | 310 | "Installation Information" for a User Product means any methods, 311 | procedures, authorization keys, or other information required to install 312 | and execute modified versions of a covered work in that User Product from 313 | a modified version of its Corresponding Source. The information must 314 | suffice to ensure that the continued functioning of the modified object 315 | code is in no case prevented or interfered with solely because 316 | modification has been made. 317 | 318 | If you convey an object code work under this section in, or with, or 319 | specifically for use in, a User Product, and the conveying occurs as 320 | part of a transaction in which the right of possession and use of the 321 | User Product is transferred to the recipient in perpetuity or for a 322 | fixed term (regardless of how the transaction is characterized), the 323 | Corresponding Source conveyed under this section must be accompanied 324 | by the Installation Information. But this requirement does not apply 325 | if neither you nor any third party retains the ability to install 326 | modified object code on the User Product (for example, the work has 327 | been installed in ROM). 328 | 329 | The requirement to provide Installation Information does not include a 330 | requirement to continue to provide support service, warranty, or updates 331 | for a work that has been modified or installed by the recipient, or for 332 | the User Product in which it has been modified or installed. Access to a 333 | network may be denied when the modification itself materially and 334 | adversely affects the operation of the network or violates the rules and 335 | protocols for communication across the network. 336 | 337 | Corresponding Source conveyed, and Installation Information provided, 338 | in accord with this section must be in a format that is publicly 339 | documented (and with an implementation available to the public in 340 | source code form), and must require no special password or key for 341 | unpacking, reading or copying. 342 | 343 | 7. Additional Terms. 344 | 345 | "Additional permissions" are terms that supplement the terms of this 346 | License by making exceptions from one or more of its conditions. 347 | Additional permissions that are applicable to the entire Program shall 348 | be treated as though they were included in this License, to the extent 349 | that they are valid under applicable law. If additional permissions 350 | apply only to part of the Program, that part may be used separately 351 | under those permissions, but the entire Program remains governed by 352 | this License without regard to the additional permissions. 353 | 354 | When you convey a copy of a covered work, you may at your option 355 | remove any additional permissions from that copy, or from any part of 356 | it. (Additional permissions may be written to require their own 357 | removal in certain cases when you modify the work.) You may place 358 | additional permissions on material, added by you to a covered work, 359 | for which you have or can give appropriate copyright permission. 360 | 361 | Notwithstanding any other provision of this License, for material you 362 | add to a covered work, you may (if authorized by the copyright holders of 363 | that material) supplement the terms of this License with terms: 364 | 365 | a) Disclaiming warranty or limiting liability differently from the 366 | terms of sections 15 and 16 of this License; or 367 | 368 | b) Requiring preservation of specified reasonable legal notices or 369 | author attributions in that material or in the Appropriate Legal 370 | Notices displayed by works containing it; or 371 | 372 | c) Prohibiting misrepresentation of the origin of that material, or 373 | requiring that modified versions of such material be marked in 374 | reasonable ways as different from the original version; or 375 | 376 | d) Limiting the use for publicity purposes of names of licensors or 377 | authors of the material; or 378 | 379 | e) Declining to grant rights under trademark law for use of some 380 | trade names, trademarks, or service marks; or 381 | 382 | f) Requiring indemnification of licensors and authors of that 383 | material by anyone who conveys the material (or modified versions of 384 | it) with contractual assumptions of liability to the recipient, for 385 | any liability that these contractual assumptions directly impose on 386 | those licensors and authors. 387 | 388 | All other non-permissive additional terms are considered "further 389 | restrictions" within the meaning of section 10. If the Program as you 390 | received it, or any part of it, contains a notice stating that it is 391 | governed by this License along with a term that is a further 392 | restriction, you may remove that term. If a license document contains 393 | a further restriction but permits relicensing or conveying under this 394 | License, you may add to a covered work material governed by the terms 395 | of that license document, provided that the further restriction does 396 | not survive such relicensing or conveying. 397 | 398 | If you add terms to a covered work in accord with this section, you 399 | must place, in the relevant source files, a statement of the 400 | additional terms that apply to those files, or a notice indicating 401 | where to find the applicable terms. 402 | 403 | Additional terms, permissive or non-permissive, may be stated in the 404 | form of a separately written license, or stated as exceptions; 405 | the above requirements apply either way. 406 | 407 | 8. Termination. 408 | 409 | You may not propagate or modify a covered work except as expressly 410 | provided under this License. Any attempt otherwise to propagate or 411 | modify it is void, and will automatically terminate your rights under 412 | this License (including any patent licenses granted under the third 413 | paragraph of section 11). 414 | 415 | However, if you cease all violation of this License, then your 416 | license from a particular copyright holder is reinstated (a) 417 | provisionally, unless and until the copyright holder explicitly and 418 | finally terminates your license, and (b) permanently, if the copyright 419 | holder fails to notify you of the violation by some reasonable means 420 | prior to 60 days after the cessation. 421 | 422 | Moreover, your license from a particular copyright holder is 423 | reinstated permanently if the copyright holder notifies you of the 424 | violation by some reasonable means, this is the first time you have 425 | received notice of violation of this License (for any work) from that 426 | copyright holder, and you cure the violation prior to 30 days after 427 | your receipt of the notice. 428 | 429 | Termination of your rights under this section does not terminate the 430 | licenses of parties who have received copies or rights from you under 431 | this License. If your rights have been terminated and not permanently 432 | reinstated, you do not qualify to receive new licenses for the same 433 | material under section 10. 434 | 435 | 9. Acceptance Not Required for Having Copies. 436 | 437 | You are not required to accept this License in order to receive or 438 | run a copy of the Program. Ancillary propagation of a covered work 439 | occurring solely as a consequence of using peer-to-peer transmission 440 | to receive a copy likewise does not require acceptance. However, 441 | nothing other than this License grants you permission to propagate or 442 | modify any covered work. These actions infringe copyright if you do 443 | not accept this License. Therefore, by modifying or propagating a 444 | covered work, you indicate your acceptance of this License to do so. 445 | 446 | 10. Automatic Licensing of Downstream Recipients. 447 | 448 | Each time you convey a covered work, the recipient automatically 449 | receives a license from the original licensors, to run, modify and 450 | propagate that work, subject to this License. You are not responsible 451 | for enforcing compliance by third parties with this License. 452 | 453 | An "entity transaction" is a transaction transferring control of an 454 | organization, or substantially all assets of one, or subdividing an 455 | organization, or merging organizations. If propagation of a covered 456 | work results from an entity transaction, each party to that 457 | transaction who receives a copy of the work also receives whatever 458 | licenses to the work the party's predecessor in interest had or could 459 | give under the previous paragraph, plus a right to possession of the 460 | Corresponding Source of the work from the predecessor in interest, if 461 | the predecessor has it or can get it with reasonable efforts. 462 | 463 | You may not impose any further restrictions on the exercise of the 464 | rights granted or affirmed under this License. For example, you may 465 | not impose a license fee, royalty, or other charge for exercise of 466 | rights granted under this License, and you may not initiate litigation 467 | (including a cross-claim or counterclaim in a lawsuit) alleging that 468 | any patent claim is infringed by making, using, selling, offering for 469 | sale, or importing the Program or any portion of it. 470 | 471 | 11. Patents. 472 | 473 | A "contributor" is a copyright holder who authorizes use under this 474 | License of the Program or a work on which the Program is based. The 475 | work thus licensed is called the contributor's "contributor version". 476 | 477 | A contributor's "essential patent claims" are all patent claims 478 | owned or controlled by the contributor, whether already acquired or 479 | hereafter acquired, that would be infringed by some manner, permitted 480 | by this License, of making, using, or selling its contributor version, 481 | but do not include claims that would be infringed only as a 482 | consequence of further modification of the contributor version. For 483 | purposes of this definition, "control" includes the right to grant 484 | patent sublicenses in a manner consistent with the requirements of 485 | this License. 486 | 487 | Each contributor grants you a non-exclusive, worldwide, royalty-free 488 | patent license under the contributor's essential patent claims, to 489 | make, use, sell, offer for sale, import and otherwise run, modify and 490 | propagate the contents of its contributor version. 491 | 492 | In the following three paragraphs, a "patent license" is any express 493 | agreement or commitment, however denominated, not to enforce a patent 494 | (such as an express permission to practice a patent or covenant not to 495 | sue for patent infringement). To "grant" such a patent license to a 496 | party means to make such an agreement or commitment not to enforce a 497 | patent against the party. 498 | 499 | If you convey a covered work, knowingly relying on a patent license, 500 | and the Corresponding Source of the work is not available for anyone 501 | to copy, free of charge and under the terms of this License, through a 502 | publicly available network server or other readily accessible means, 503 | then you must either (1) cause the Corresponding Source to be so 504 | available, or (2) arrange to deprive yourself of the benefit of the 505 | patent license for this particular work, or (3) arrange, in a manner 506 | consistent with the requirements of this License, to extend the patent 507 | license to downstream recipients. "Knowingly relying" means you have 508 | actual knowledge that, but for the patent license, your conveying the 509 | covered work in a country, or your recipient's use of the covered work 510 | in a country, would infringe one or more identifiable patents in that 511 | country that you have reason to believe are valid. 512 | 513 | If, pursuant to or in connection with a single transaction or 514 | arrangement, you convey, or propagate by procuring conveyance of, a 515 | covered work, and grant a patent license to some of the parties 516 | receiving the covered work authorizing them to use, propagate, modify 517 | or convey a specific copy of the covered work, then the patent license 518 | you grant is automatically extended to all recipients of the covered 519 | work and works based on it. 520 | 521 | A patent license is "discriminatory" if it does not include within 522 | the scope of its coverage, prohibits the exercise of, or is 523 | conditioned on the non-exercise of one or more of the rights that are 524 | specifically granted under this License. You may not convey a covered 525 | work if you are a party to an arrangement with a third party that is 526 | in the business of distributing software, under which you make payment 527 | to the third party based on the extent of your activity of conveying 528 | the work, and under which the third party grants, to any of the 529 | parties who would receive the covered work from you, a discriminatory 530 | patent license (a) in connection with copies of the covered work 531 | conveyed by you (or copies made from those copies), or (b) primarily 532 | for and in connection with specific products or compilations that 533 | contain the covered work, unless you entered into that arrangement, 534 | or that patent license was granted, prior to 28 March 2007. 535 | 536 | Nothing in this License shall be construed as excluding or limiting 537 | any implied license or other defenses to infringement that may 538 | otherwise be available to you under applicable patent law. 539 | 540 | 12. No Surrender of Others' Freedom. 541 | 542 | If conditions are imposed on you (whether by court order, agreement or 543 | otherwise) that contradict the conditions of this License, they do not 544 | excuse you from the conditions of this License. If you cannot convey a 545 | covered work so as to satisfy simultaneously your obligations under this 546 | License and any other pertinent obligations, then as a consequence you may 547 | not convey it at all. For example, if you agree to terms that obligate you 548 | to collect a royalty for further conveying from those to whom you convey 549 | the Program, the only way you could satisfy both those terms and this 550 | License would be to refrain entirely from conveying the Program. 551 | 552 | 13. Use with the GNU Affero General Public License. 553 | 554 | Notwithstanding any other provision of this License, you have 555 | permission to link or combine any covered work with a work licensed 556 | under version 3 of the GNU Affero General Public License into a single 557 | combined work, and to convey the resulting work. The terms of this 558 | License will continue to apply to the part which is the covered work, 559 | but the special requirements of the GNU Affero General Public License, 560 | section 13, concerning interaction through a network will apply to the 561 | combination as such. 562 | 563 | 14. Revised Versions of this License. 564 | 565 | The Free Software Foundation may publish revised and/or new versions of 566 | the GNU General Public License from time to time. Such new versions will 567 | be similar in spirit to the present version, but may differ in detail to 568 | address new problems or concerns. 569 | 570 | Each version is given a distinguishing version number. If the 571 | Program specifies that a certain numbered version of the GNU General 572 | Public License "or any later version" applies to it, you have the 573 | option of following the terms and conditions either of that numbered 574 | version or of any later version published by the Free Software 575 | Foundation. If the Program does not specify a version number of the 576 | GNU General Public License, you may choose any version ever published 577 | by the Free Software Foundation. 578 | 579 | If the Program specifies that a proxy can decide which future 580 | versions of the GNU General Public License can be used, that proxy's 581 | public statement of acceptance of a version permanently authorizes you 582 | to choose that version for the Program. 583 | 584 | Later license versions may give you additional or different 585 | permissions. However, no additional obligations are imposed on any 586 | author or copyright holder as a result of your choosing to follow a 587 | later version. 588 | 589 | 15. Disclaimer of Warranty. 590 | 591 | THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY 592 | APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT 593 | HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY 594 | OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, 595 | THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 596 | PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM 597 | IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF 598 | ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 599 | 600 | 16. Limitation of Liability. 601 | 602 | IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING 603 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS 604 | THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY 605 | GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE 606 | USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF 607 | DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD 608 | PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), 609 | EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF 610 | SUCH DAMAGES. 611 | 612 | 17. Interpretation of Sections 15 and 16. 613 | 614 | If the disclaimer of warranty and limitation of liability provided 615 | above cannot be given local legal effect according to their terms, 616 | reviewing courts shall apply local law that most closely approximates 617 | an absolute waiver of all civil liability in connection with the 618 | Program, unless a warranty or assumption of liability accompanies a 619 | copy of the Program in return for a fee. 620 | 621 | END OF TERMS AND CONDITIONS 622 | 623 | How to Apply These Terms to Your New Programs 624 | 625 | If you develop a new program, and you want it to be of the greatest 626 | possible use to the public, the best way to achieve this is to make it 627 | free software which everyone can redistribute and change under these terms. 628 | 629 | To do so, attach the following notices to the program. It is safest 630 | to attach them to the start of each source file to most effectively 631 | state the exclusion of warranty; and each file should have at least 632 | the "copyright" line and a pointer to where the full notice is found. 633 | 634 | 635 | Copyright (C) 636 | 637 | This program is free software: you can redistribute it and/or modify 638 | it under the terms of the GNU General Public License as published by 639 | the Free Software Foundation, either version 3 of the License, or 640 | (at your option) any later version. 641 | 642 | This program is distributed in the hope that it will be useful, 643 | but WITHOUT ANY WARRANTY; without even the implied warranty of 644 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 645 | GNU General Public License for more details. 646 | 647 | You should have received a copy of the GNU General Public License 648 | along with this program. If not, see . 649 | 650 | Also add information on how to contact you by electronic and paper mail. 651 | 652 | If the program does terminal interaction, make it output a short 653 | notice like this when it starts in an interactive mode: 654 | 655 | Copyright (C) 656 | This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. 657 | This is free software, and you are welcome to redistribute it 658 | under certain conditions; type `show c' for details. 659 | 660 | The hypothetical commands `show w' and `show c' should show the appropriate 661 | parts of the General Public License. Of course, your program's commands 662 | might be different; for a GUI interface, you would use an "about box". 663 | 664 | You should also get your employer (if you work as a programmer) or school, 665 | if any, to sign a "copyright disclaimer" for the program, if necessary. 666 | For more information on this, and how to apply and follow the GNU GPL, see 667 | . 668 | 669 | The GNU General Public License does not permit incorporating your program 670 | into proprietary programs. If your program is a subroutine library, you 671 | may consider it more useful to permit linking proprietary applications with 672 | the library. If this is what you want to do, use the GNU Lesser General 673 | Public License instead of this License. But first, please read 674 | . 675 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Kubesec - Relatórios de Segurança para Clusters Kubernetes 2 | 3 | O projeto Kubesec é uma solução abrangente para análise e relatórios de segurança em clusters Kubernetes. Ele combina várias ferramentas populares, como o marvin, kube-bench, kubescan e popeye, para fornecer insights detalhados sobre a segurança do seu ambiente Kubernetes. O projeto automatiza a execução dessas ferramentas e gera relatórios claros e informativos para ajudar os administradores de clusters a entender e melhorar a postura de segurança de seus clusters. 4 | 5 | ## Introdução 6 | 7 | Manter a segurança em clusters Kubernetes é uma tarefa crítica para garantir que suas aplicações e dados estejam protegidos. O projeto Kubesec foi desenvolvido para facilitar essa tarefa, fornecendo uma solução abrangente para avaliação e geração de relatórios de segurança. 8 | 9 | ## Ferramentas Incluídas 10 | 11 | O Kubesec utiliza as seguintes ferramentas para análise de segurança: 12 | 13 | - [marvin](https://github.com/undistro/marvin): Ferramenta de segurança para Kubernetes que verifica vulnerabilidades em imagens de contêineres e seus artefatos. 14 | - [popeye](https://github.com/derailed/popeye): Ferramenta que analisa clusters Kubernetes em busca de problemas de configuração e recursos ociosos. 15 | - [kube-hunter](https://github.com/aquasecurity/kube-hunter): Ferramenta que executa testes de segurança em clusters Kubernetes para identificar possíveis vulnerabilidades. 16 | - [kube-bench](https://github.com/aquasecurity/kube-bench): Ferramenta que verifica a conformidade do cluster Kubernetes com os benchmarks do CIS. 17 | 18 | ## Pré-requisitos 19 | 20 | - kubectl: A ferramenta de linha de comando Kubernetes (kubectl) é essencial para interagir com e gerenciar clusters Kubernetes.`Para realizar sua instalação: 21 | 22 | ``` 23 | sudo apt-get update 24 | sudo apt-get install kubectl 25 | ``` 26 | 27 | - curl: O utilitário de linha de comando curl é usado para fazer requisições de transferência de dados por URL. Para realizar sua instalação: 28 | 29 | ``` 30 | sudo apt-get update 31 | sudo apt-get install curl 32 | ``` 33 | 34 | - pandoc: O Pandoc é uma ferramenta de conversão de documentos que pode ser usada para converter entre diferentes formatos de arquivo, como Markdown para PDF. Para realizar sua instalação: 35 | 36 | ``` 37 | sudo apt-get update 38 | sudo apt-get install pandoc 39 | ``` 40 | 41 | Para melhor visualizar os relatórios do popeye: 42 | 43 | ``` 44 | export TERM=xterm-256color 45 | ``` 46 | 47 | ## Instruções de Uso 48 | 49 | 1. Clone este repositório em sua máquina local: 50 | 51 | ``` 52 | git clone https://github.com/nataliagranato/kubesec.git 53 | ``` 54 | 55 | 2. Navegue para o diretório do projeto: 56 | 57 | ``` 58 | cd kubesec 59 | ``` 60 | 61 | ## Geração de relatórios 62 | 63 | - Executar o ./kube-bench para avaliar a conformidade do cluster com os benchmarks do CIS. 64 | 65 | - Executar o ./kube-hunter para identificar possíveis vulnerabilidades no cluster. 66 | - Executar o ./marvin para analisar as imagens de contêineres em busca de vulnerabilidades. 67 | - Executar o ./popeye para identificar problemas de configuração e recursos ociosos. 68 | 69 | ## Contribuição 70 | 71 | Contribuições são bem-vindas! Se você deseja adicionar novos scripts, aprimorar os existentes ou sugerir melhorias, sinta-se à vontade para criar um pull request. 72 | 73 | ## Licença 74 | 75 | Este projeto é licenciado sob a [GNU General Public License v3.0](https://github.com/nataliagranato/kubeshell/blob/main/LICENSE). 76 | -------------------------------------------------------------------------------- /scripts/.gitignore: -------------------------------------------------------------------------------- 1 | kube-bench-scan.pdf 2 | kube-bench-scan.txt 3 | kube-hunter-scan.pdf 4 | kube-hunter-scan.txt 5 | marvin-scan.txt 6 | report.html 7 | -------------------------------------------------------------------------------- /scripts/kube-bench-scan.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Tech-Preta/kubesec/a7f455a7ac7b5a2d435c6a1e38ae8733989770ee/scripts/kube-bench-scan.pdf -------------------------------------------------------------------------------- /scripts/kube-bench-scan.txt: -------------------------------------------------------------------------------- 1 | [INFO] 4 Worker Node Security Configuration 2 | [INFO] 4.1 Worker Node Configuration Files 3 | [FAIL] 4.1.1 Ensure that the kubelet service file permissions are set to 600 or more restrictive (Automated) 4 | [PASS] 4.1.2 Ensure that the kubelet service file ownership is set to root:root (Automated) 5 | [PASS] 4.1.3 If proxy kubeconfig file exists ensure permissions are set to 600 or more restrictive (Manual) 6 | [PASS] 4.1.4 If proxy kubeconfig file exists ensure ownership is set to root:root (Manual) 7 | [PASS] 4.1.5 Ensure that the --kubeconfig kubelet.conf file permissions are set to 600 or more restrictive (Automated) 8 | [PASS] 4.1.6 Ensure that the --kubeconfig kubelet.conf file ownership is set to root:root (Automated) 9 | [WARN] 4.1.7 Ensure that the certificate authorities file permissions are set to 600 or more restrictive (Manual) 10 | [WARN] 4.1.8 Ensure that the client certificate authorities file ownership is set to root:root (Manual) 11 | [WARN] 4.1.9 If the kubelet config.yaml configuration file is being used validate permissions set to 600 or more restrictive (Manual) 12 | [PASS] 4.1.10 If the kubelet config.yaml configuration file is being used validate file ownership is set to root:root (Manual) 13 | [INFO] 4.2 Kubelet 14 | [FAIL] 4.2.1 Ensure that the --anonymous-auth argument is set to false (Automated) 15 | [FAIL] 4.2.2 Ensure that the --authorization-mode argument is not set to AlwaysAllow (Automated) 16 | [FAIL] 4.2.3 Ensure that the --client-ca-file argument is set as appropriate (Automated) 17 | [PASS] 4.2.4 Verify that the --read-only-port argument is set to 0 (Manual) 18 | [PASS] 4.2.5 Ensure that the --streaming-connection-idle-timeout argument is not set to 0 (Manual) 19 | [FAIL] 4.2.6 Ensure that the --protect-kernel-defaults argument is set to true (Automated) 20 | [PASS] 4.2.7 Ensure that the --make-iptables-util-chains argument is set to true (Automated) 21 | [WARN] 4.2.8 Ensure that the --hostname-override argument is not set (Manual) 22 | [PASS] 4.2.9 Ensure that the eventRecordQPS argument is set to a level which ensures appropriate event capture (Manual) 23 | [WARN] 4.2.10 Ensure that the --tls-cert-file and --tls-private-key-file arguments are set as appropriate (Manual) 24 | [PASS] 4.2.11 Ensure that the --rotate-certificates argument is not set to false (Automated) 25 | [PASS] 4.2.12 Verify that the RotateKubeletServerCertificate argument is set to true (Manual) 26 | [WARN] 4.2.13 Ensure that the Kubelet only makes use of Strong Cryptographic Ciphers (Manual) 27 | 28 | == Remediations node == 29 | 4.1.1 Run the below command (based on the file location on your system) on the each worker node. 30 | For example, chmod 600 /etc/systemd/system/kubelet.service 31 | 32 | 4.1.7 Run the following command to modify the file permissions of the 33 | --client-ca-file chmod 600 34 | 35 | 4.1.8 Run the following command to modify the ownership of the --client-ca-file. 36 | chown root:root 37 | 38 | 4.1.9 Run the following command (using the config file location identified in the Audit step) 39 | chmod 600 /etc/systemd/system/kubelet.service 40 | 41 | 4.2.1 If using a Kubelet config file, edit the file to set `authentication: anonymous: enabled` to 42 | `false`. 43 | If using executable arguments, edit the kubelet service file 44 | /etc/systemd/system/kubelet.service on each worker node and 45 | set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable. 46 | `--anonymous-auth=false` 47 | Based on your system, restart the kubelet service. For example, 48 | systemctl daemon-reload 49 | systemctl restart kubelet.service 50 | 51 | 4.2.2 If using a Kubelet config file, edit the file to set `authorization.mode` to Webhook. If 52 | using executable arguments, edit the kubelet service file 53 | /etc/systemd/system/kubelet.service on each worker node and 54 | set the below parameter in KUBELET_AUTHZ_ARGS variable. 55 | --authorization-mode=Webhook 56 | Based on your system, restart the kubelet service. For example, 57 | systemctl daemon-reload 58 | systemctl restart kubelet.service 59 | 60 | 4.2.3 If using a Kubelet config file, edit the file to set `authentication.x509.clientCAFile` to 61 | the location of the client CA file. 62 | If using command line arguments, edit the kubelet service file 63 | /etc/systemd/system/kubelet.service on each worker node and 64 | set the below parameter in KUBELET_AUTHZ_ARGS variable. 65 | --client-ca-file= 66 | Based on your system, restart the kubelet service. For example, 67 | systemctl daemon-reload 68 | systemctl restart kubelet.service 69 | 70 | 4.2.6 If using a Kubelet config file, edit the file to set `protectKernelDefaults` to `true`. 71 | If using command line arguments, edit the kubelet service file 72 | /etc/systemd/system/kubelet.service on each worker node and 73 | set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable. 74 | --protect-kernel-defaults=true 75 | Based on your system, restart the kubelet service. For example: 76 | systemctl daemon-reload 77 | systemctl restart kubelet.service 78 | 79 | 4.2.8 Edit the kubelet service file /etc/systemd/system/kubelet.service 80 | on each worker node and remove the --hostname-override argument from the 81 | KUBELET_SYSTEM_PODS_ARGS variable. 82 | Based on your system, restart the kubelet service. For example, 83 | systemctl daemon-reload 84 | systemctl restart kubelet.service 85 | 86 | 4.2.10 If using a Kubelet config file, edit the file to set `tlsCertFile` to the location 87 | of the certificate file to use to identify this Kubelet, and `tlsPrivateKeyFile` 88 | to the location of the corresponding private key file. 89 | If using command line arguments, edit the kubelet service file 90 | /etc/systemd/system/kubelet.service on each worker node and 91 | set the below parameters in KUBELET_CERTIFICATE_ARGS variable. 92 | --tls-cert-file= 93 | --tls-private-key-file= 94 | Based on your system, restart the kubelet service. For example, 95 | systemctl daemon-reload 96 | systemctl restart kubelet.service 97 | 98 | 4.2.13 If using a Kubelet config file, edit the file to set `TLSCipherSuites` to 99 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256 100 | or to a subset of these values. 101 | If using executable arguments, edit the kubelet service file 102 | /etc/systemd/system/kubelet.service on each worker node and 103 | set the --tls-cipher-suites parameter as follows, or to a subset of these values. 104 | --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256 105 | Based on your system, restart the kubelet service. For example: 106 | systemctl daemon-reload 107 | systemctl restart kubelet.service 108 | 109 | 110 | == Summary node == 111 | 12 checks PASS 112 | 5 checks FAIL 113 | 6 checks WARN 114 | 0 checks INFO 115 | 116 | [INFO] 5 Kubernetes Policies 117 | [INFO] 5.1 RBAC and Service Accounts 118 | [WARN] 5.1.1 Ensure that the cluster-admin role is only used where required (Manual) 119 | [WARN] 5.1.2 Minimize access to secrets (Manual) 120 | [WARN] 5.1.3 Minimize wildcard use in Roles and ClusterRoles (Manual) 121 | [WARN] 5.1.4 Minimize access to create pods (Manual) 122 | [WARN] 5.1.5 Ensure that default service accounts are not actively used. (Manual) 123 | [WARN] 5.1.6 Ensure that Service Account Tokens are only mounted where necessary (Manual) 124 | [WARN] 5.1.7 Avoid use of system:masters group (Manual) 125 | [WARN] 5.1.8 Limit use of the Bind, Impersonate and Escalate permissions in the Kubernetes cluster (Manual) 126 | [INFO] 5.2 Pod Security Standards 127 | [WARN] 5.2.1 Ensure that the cluster has at least one active policy control mechanism in place (Manual) 128 | [WARN] 5.2.2 Minimize the admission of privileged containers (Manual) 129 | [WARN] 5.2.3 Minimize the admission of containers wishing to share the host process ID namespace (Automated) 130 | [WARN] 5.2.4 Minimize the admission of containers wishing to share the host IPC namespace (Automated) 131 | [WARN] 5.2.5 Minimize the admission of containers wishing to share the host network namespace (Automated) 132 | [WARN] 5.2.6 Minimize the admission of containers with allowPrivilegeEscalation (Automated) 133 | [WARN] 5.2.7 Minimize the admission of root containers (Automated) 134 | [WARN] 5.2.8 Minimize the admission of containers with the NET_RAW capability (Automated) 135 | [WARN] 5.2.9 Minimize the admission of containers with added capabilities (Automated) 136 | [WARN] 5.2.10 Minimize the admission of containers with capabilities assigned (Manual) 137 | [WARN] 5.2.11 Minimize the admission of Windows HostProcess containers (Manual) 138 | [WARN] 5.2.12 Minimize the admission of HostPath volumes (Manual) 139 | [WARN] 5.2.13 Minimize the admission of containers which use HostPorts (Manual) 140 | [INFO] 5.3 Network Policies and CNI 141 | [WARN] 5.3.1 Ensure that the CNI in use supports NetworkPolicies (Manual) 142 | [WARN] 5.3.2 Ensure that all Namespaces have NetworkPolicies defined (Manual) 143 | [INFO] 5.4 Secrets Management 144 | [WARN] 5.4.1 Prefer using Secrets as files over Secrets as environment variables (Manual) 145 | [WARN] 5.4.2 Consider external secret storage (Manual) 146 | [INFO] 5.5 Extensible Admission Control 147 | [WARN] 5.5.1 Configure Image Provenance using ImagePolicyWebhook admission controller (Manual) 148 | [INFO] 5.7 General Policies 149 | [WARN] 5.7.1 Create administrative boundaries between resources using namespaces (Manual) 150 | [WARN] 5.7.2 Ensure that the seccomp profile is set to docker/default in your Pod definitions (Manual) 151 | [WARN] 5.7.3 Apply SecurityContext to your Pods and Containers (Manual) 152 | [WARN] 5.7.4 The default namespace should not be used (Manual) 153 | 154 | == Remediations policies == 155 | 5.1.1 Identify all clusterrolebindings to the cluster-admin role. Check if they are used and 156 | if they need this role or if they could use a role with fewer privileges. 157 | Where possible, first bind users to a lower privileged role and then remove the 158 | clusterrolebinding to the cluster-admin role : 159 | kubectl delete clusterrolebinding [name] 160 | 161 | 5.1.2 Where possible, remove get, list and watch access to Secret objects in the cluster. 162 | 163 | 5.1.3 Where possible replace any use of wildcards in clusterroles and roles with specific 164 | objects or actions. 165 | 166 | 5.1.4 Where possible, remove create access to pod objects in the cluster. 167 | 168 | 5.1.5 Create explicit service accounts wherever a Kubernetes workload requires specific access 169 | to the Kubernetes API server. 170 | Modify the configuration of each default service account to include this value 171 | automountServiceAccountToken: false 172 | 173 | 5.1.6 Modify the definition of pods and service accounts which do not need to mount service 174 | account tokens to disable it. 175 | 176 | 5.1.7 Remove the system:masters group from all users in the cluster. 177 | 178 | 5.1.8 Where possible, remove the impersonate, bind and escalate rights from subjects. 179 | 180 | 5.2.1 Ensure that either Pod Security Admission or an external policy control system is in place 181 | for every namespace which contains user workloads. 182 | 183 | 5.2.2 Add policies to each namespace in the cluster which has user workloads to restrict the 184 | admission of privileged containers. 185 | 186 | 5.2.3 Add policies to each namespace in the cluster which has user workloads to restrict the 187 | admission of `hostPID` containers. 188 | 189 | 5.2.4 Add policies to each namespace in the cluster which has user workloads to restrict the 190 | admission of `hostIPC` containers. 191 | 192 | 5.2.5 Add policies to each namespace in the cluster which has user workloads to restrict the 193 | admission of `hostNetwork` containers. 194 | 195 | 5.2.6 Add policies to each namespace in the cluster which has user workloads to restrict the 196 | admission of containers with `.spec.allowPrivilegeEscalation` set to `true`. 197 | 198 | 5.2.7 Create a policy for each namespace in the cluster, ensuring that either `MustRunAsNonRoot` 199 | or `MustRunAs` with the range of UIDs not including 0, is set. 200 | 201 | 5.2.8 Add policies to each namespace in the cluster which has user workloads to restrict the 202 | admission of containers with the `NET_RAW` capability. 203 | 204 | 5.2.9 Ensure that `allowedCapabilities` is not present in policies for the cluster unless 205 | it is set to an empty array. 206 | 207 | 5.2.10 Review the use of capabilites in applications running on your cluster. Where a namespace 208 | contains applicaions which do not require any Linux capabities to operate consider adding 209 | a PSP which forbids the admission of containers which do not drop all capabilities. 210 | 211 | 5.2.11 Add policies to each namespace in the cluster which has user workloads to restrict the 212 | admission of containers that have `.securityContext.windowsOptions.hostProcess` set to `true`. 213 | 214 | 5.2.12 Add policies to each namespace in the cluster which has user workloads to restrict the 215 | admission of containers with `hostPath` volumes. 216 | 217 | 5.2.13 Add policies to each namespace in the cluster which has user workloads to restrict the 218 | admission of containers which use `hostPort` sections. 219 | 220 | 5.3.1 If the CNI plugin in use does not support network policies, consideration should be given to 221 | making use of a different plugin, or finding an alternate mechanism for restricting traffic 222 | in the Kubernetes cluster. 223 | 224 | 5.3.2 Follow the documentation and create NetworkPolicy objects as you need them. 225 | 226 | 5.4.1 If possible, rewrite application code to read Secrets from mounted secret files, rather than 227 | from environment variables. 228 | 229 | 5.4.2 Refer to the Secrets management options offered by your cloud provider or a third-party 230 | secrets management solution. 231 | 232 | 5.5.1 Follow the Kubernetes documentation and setup image provenance. 233 | 234 | 5.7.1 Follow the documentation and create namespaces for objects in your deployment as you need 235 | them. 236 | 237 | 5.7.2 Use `securityContext` to enable the docker/default seccomp profile in your pod definitions. 238 | An example is as below: 239 | securityContext: 240 | seccompProfile: 241 | type: RuntimeDefault 242 | 243 | 5.7.3 Follow the Kubernetes documentation and apply SecurityContexts to your Pods. For a 244 | suggested list of SecurityContexts, you may refer to the CIS Security Benchmark for Docker 245 | Containers. 246 | 247 | 5.7.4 Ensure that namespaces are created to allow for appropriate segregation of Kubernetes 248 | resources and that all new resources are created in a specific namespace. 249 | 250 | 251 | == Summary policies == 252 | 0 checks PASS 253 | 0 checks FAIL 254 | 30 checks WARN 255 | 0 checks INFO 256 | 257 | == Summary total == 258 | 12 checks PASS 259 | 5 checks FAIL 260 | 36 checks WARN 261 | 0 checks INFO 262 | 263 | -------------------------------------------------------------------------------- /scripts/kube-bench.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | 3 | # Verifica se o kubectl está instalado 4 | kubectl_installed=$(command -v kubectl) 5 | 6 | if [ -z "$kubectl_installed" ]; then 7 | echo "O kubectl não está instalado no seu sistema." 8 | else 9 | echo "Instalando o kube-bench no namespace default..." 10 | 11 | # Aplicação do kube-bench.yaml 12 | kubectl apply -f https://raw.githubusercontent.com/aquasecurity/kube-bench/master/job.yaml 13 | 14 | echo "Esperando o kube-bench concluir..." 15 | sleep 10 16 | 17 | echo "Visualizando e salvando os logs do kube-bench..." 18 | 19 | # Obtendo o nome do pod kube-bench 20 | pod_name=$(kubectl get pods -n default -l app=kube-bench,job-name=kube-bench -o jsonpath='{.items[0].metadata.name}') 21 | 22 | # Obtendo os logs do pod 23 | kubectl logs -n default "$pod_name" > kube-bench-scan.txt 24 | 25 | echo "Logs do pod $pod_name foram salvos no arquivo kube-bench-scan.txt" 26 | 27 | # Convertendo o arquivo de log para PDF usando pandoc (requer pandoc instalado) 28 | pandoc -o kube-bench-scan.pdf kube-bench-scan.txt 29 | echo "Arquivo kube-bench-scan.pdf foi criado." 30 | fi 31 | 32 | -------------------------------------------------------------------------------- /scripts/kube-hunter-scan.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Tech-Preta/kubesec/a7f455a7ac7b5a2d435c6a1e38ae8733989770ee/scripts/kube-hunter-scan.pdf -------------------------------------------------------------------------------- /scripts/kube-hunter-scan.txt: -------------------------------------------------------------------------------- 1 | Choose one of the options below: 2 | 1. Remote scanning (scans one or more specific IPs or DNS names) 3 | 2. Interface scanning (scans subnets on all local network interfaces) 4 | 3. IP range scanning (scans a given IP range) 5 | Your choice: -------------------------------------------------------------------------------- /scripts/kube-hunter.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | 3 | # Verifica se o kubectl está instalado 4 | kubectl_installed=$(command -v kubectl) 5 | 6 | if [ -z "$kubectl_installed" ]; then 7 | echo "O kubectl não está instalado no seu sistema." 8 | else 9 | echo "Instalando o kube-hunter no namespace default..." 10 | 11 | # Aplicação do kube-hunter.yaml 12 | kubectl apply -f https://raw.githubusercontent.com/aquasecurity/kube-hunter/master/job.yaml 13 | 14 | echo "Esperando o kube-hunter concluir..." 15 | sleep 10 16 | 17 | echo "Executando o kube-hunter..." 18 | 19 | # Obtendo o nome do pod kube-hunter 20 | pod_name=$(kubectl get pods -n default -l app=kube-hunter -o jsonpath='{.items[0].metadata.name}') 21 | 22 | # Executando o kube-hunter 23 | kubectl exec -n default "$pod_name" kube-hunter > kube-hunter-scan.txt 24 | 25 | echo "Resultado do kube-hunter foi salvo no arquivo kube-hunter-scan.txt" 26 | 27 | # Convertendo o arquivo de log para PDF usando pandoc (requer pandoc instalado) 28 | pandoc -o kube-hunter-scan.pdf kube-hunter-scan.txt 29 | echo "Arquivo kube-hunter-scan.pdf foi criado." 30 | fi 31 | -------------------------------------------------------------------------------- /scripts/marvin-scan.txt: -------------------------------------------------------------------------------- 1 | SEVERITY ID CHECK STATUS FAILED PASSED SKIPPED 2 | High M-201 Application credentials stored in configuration files Failed 167 651 0 3 | High M-104 HostPath volume Failed 123 426 0 4 | High M-101 Host namespaces Failed 102 447 0 5 | High M-102 Privileged container Failed 88 461 0 6 | High M-105 Not allowed hostPort Failed 25 524 0 7 | High M-103 Insecure capabilities Failed 12 537 0 8 | High M-100 Privileged access to the Windows node Passed 0 549 0 9 | Medium M-407 CPU not limited Failed 487 62 0 10 | Medium M-405 CPU requests not specified Failed 383 166 0 11 | Medium M-406 Memory not limited Failed 383 166 0 12 | Medium M-404 Memory requests not specified Failed 369 180 0 13 | Medium M-113 Container could be running as root user Failed 330 219 0 14 | Medium M-403 Liveness probe not configured Failed 289 249 0 15 | Medium M-402 Readiness and startup probe not configured Failed 270 268 0 16 | Medium M-400 Image tagged latest Failed 27 522 0 17 | Medium M-112 Allowed privilege escalation Failed 12 537 0 18 | Medium M-106 Forbidden AppArmor profile Passed 0 549 0 19 | Medium M-107 Forbidden SELinux options Passed 0 549 0 20 | Medium M-108 Forbidden proc mount type Passed 0 549 0 21 | Medium M-109 Forbidden seccomp profile Passed 0 549 0 22 | Medium M-110 Unsafe sysctls Passed 0 549 0 23 | Medium M-200 Image registry not allowed Passed 0 549 0 24 | Low M-202 Automounted service account token Failed 511 38 0 25 | Low M-115 Not allowed seccomp profile Failed 509 40 0 26 | Low M-116 Not allowed added/dropped capabilities Failed 483 66 0 27 | Low M-300 Root filesystem write allowed Failed 394 155 0 28 | Low M-111 Not allowed volume type Failed 123 426 0 29 | Low M-114 Container running as root UID Failed 45 504 0 30 | Low M-401 Unmanaged Pod Failed 1 255 0 31 | Low M-203 SSH server running inside container Passed 0 698 0 32 |  33 | Now you can use Marvin as a Zora plugin and see the results in a dashboard. 34 | Access the documentation for more details: https://zora-docs.undistro.io 35 | 36 |  -------------------------------------------------------------------------------- /scripts/marvin.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | 3 | echo "Verificando se o marvin está instalado..." 4 | 5 | # Verificando se o marvin CLI está instalado 6 | if ! command -v marvin &>/dev/null; then 7 | echo "O marvin não está instalado. Baixando e instalando o marvin..." 8 | 9 | # Baixando o marvin CLI 10 | curl -sSfL -o marvin https://github.com/undistro/marvin/releases/latest/download/marvin-$(uname -s)-$(uname -m) 11 | fi 12 | 13 | echo "Executando o scan com o marvin..." 14 | 15 | # Executando o scan com o marvin 16 | marvin scan > marvin-scan.txt 17 | 18 | echo "Resultado do scan do marvin foi salvo no arquivo marvin-scan.txt" 19 | 20 | # Convertendo o arquivo de log para PDF usando pandoc (requer pandoc instalado) 21 | pandoc -o marvin-scan.pdf marvin-scan.txt 22 | echo "Arquivo marvin-scan.pdf foi criado." 23 | -------------------------------------------------------------------------------- /scripts/popeye.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | 3 | echo "Verificando se o popeye está instalado..." 4 | 5 | # Verificando se o popeye está instalado 6 | if ! command -v popeye &>/dev/null; then 7 | echo "O popeye não está instalado. Baixando e instalando o popeye..." 8 | 9 | # Baixando o popeye 10 | curl -sSfL -o popeye.tar.gz https://github.com/derailed/popeye/releases/latest/download/popeye-linux-amd64.tar.gz 11 | tar -xzf popeye.tar.gz 12 | chmod +x popeye 13 | 14 | # Movendo o binário do popeye para a pasta correta 15 | mv popeye ~/.local/bin/ 16 | 17 | echo "Popeye foi instalado." 18 | fi 19 | 20 | echo "Executando o popeye e gerando o relatório em HTML..." 21 | 22 | # Executando o popeye e gerando o relatório em HTML 23 | POPEYE_REPORT_DIR=$(pwd) popeye --save --out html --output-file report.html 24 | 25 | echo "Relatório HTML do popeye foi gerado." 26 | --------------------------------------------------------------------------------